> > What about an option to allways add DB_KEY to the outer select, and
> > if this is True, not use auto-key-links at all? This way, we can
> > have an updateable resultset in an easy way ( as I understand from
> > Claudios documets ) for even the more complex statements... Right?
>
> DB_KEY has its own set of problems in a situation like IB_Query - in
> regard to being able to insert, see my previous post. DB_KEY is good

True ...

> in some circumstances but it is not the panacea.
>
> Personally I think that such an option can be left to the developer
> if that is the sort of behaviour they want. I would rather try and
> resolve the problem as Jason originally intended, either by improving
> the parsing or by separate prepare - see response to Norman.

That would surely fix the problem and it would be fine by me...

But I would add a boolean, like this:

..
KeyLinksAutoDefine is true AND
not explicit KeyLinks are given AND
... RequestLive AND ...
the primary key fields appear (via the simple POS test)
to be in the select SQL.

I added the RequestLive property - that does make sense, right?


--
Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."