Martijn,

What was fixed in IBO was the underlying problem of IBO not putting the
locate query on the server together correctly. When doing that I have to
take into consideration of the underlying column name because that is the
data I need to look through. I believe it will allow the locate on either
the underlying SQLName or the actual AliasName of the column as far as
identifying what column is being searched against.

Obviously, if there is ambiguity that the alias is required to distinguish,
then it is the responsibility of the programmer to be sure they do the
locate based on the alias and not the potentially ambiguous SQLName.

Jason

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Martijn Tonies
> Sent: Thursday, December 21, 2006 5:41 AM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] Locate problem with beta 4.7 beta 11
>
>
>
>
> > Trond wrote:
> > > SQL :
> > >
> > > SELECT RDB$USER AS AUser, RDB$RELATION_NAME AS Rolle
> > > FROM RDB$USER_PRIVILEGES
> > >
> > > iboquery1.Locate( 'RDB$USER', 'Test', [] );
> > >
> > > will fail becaus of the the alias use :(
> > >
> > > There is no keylinks etc in the query
> >
> > This is fixed in IBO 4.7 Beta 12.
>
> How? Is RDB$USER allowed in .Locate? IMO, it shouldn't, because
> of the alias. You're not searching for RDB$USER, but you are
> transforming
> column RDB$USER into derived column AUser.
>
> 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