> > I'm trying to execute the following from a TIBOQuery:
> >
> > select r.*
> > from rdb$database r
> >
> > in the SQL Monitor, I see this going to the server:
> >
> > select r.*
> > , RDB$DATABASE.RDB$DB_KEY
> > from rdb$database r
> >
> > It is a live query.
> >
> >
> > And if I execute this:
> >
> > select r.*, r.RDB$DB_KEY
> > from rdb$database r
> >
> > Then this gets to the server:
> >
> > select r.*
> > , r.RDB$DB_KEY
> > , RDB$DATABASE.RDB$DB_KEY
> > from rdb$database r
> >
> > Would this be wrong, ok or what?
>
> That doesn't look right. This portion of IBO where it automatically adds
> the DB_KEY to serve as the KeyLinks is not properly recognizing the use of
> an alias for the table. I need to update that portion of code to work
> properly. For now, your work around is to set KeyLinksAutoDefine to false
> so that IBO will not add this column. This may have other side affects,

but

> it would eliminate this immediate problem until I get it fixed.

Well, given that I can never define keylinks myself, I need them to be
autodefined :-)

Please fix this :-)

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com