Martijn Tonies:

> > > When executing this statement:
> > > select next value for category_id
> > > from rdb$database
> > >
> > > IBO mogrifies it into:
> > >
> > > select next value
> > > , RDB$DATABASE.RDB$DB_KEY
> > >
> > > I'm unsure if this has been fixed yet.

Jason Wharton:

> > I decided this bug needed to be fixed
> > prior to my new release...
> >
> > And, I have a fix for this ready now.
> >
> > I'd like someone to test it out to help me
> > make sure it works for them and that nothing
> > else gets broken. It was a pretty major surgury
> > in the parsing engine. I had to make it so that
> > it would work with multiple word tokens.
> > Before, when looking for the FOR UPDATE clause
> > of an SQL statement, I simply assumed any clause
> > that began with FOR would be it. This is now a
> > potentially fatal assumption so I enhanced my
> > parsing routines so that instead of looking for
> > FOR I can look for FOR UPDATE. I also made it
> > tolerant of any flavor of whitespace and even
> > comments between the FOR and the UPDATE.

Martijn Tonies:

> Is there an IB_SQL we can download compiled with this version of IBO?
>
> That way, we could test our statements easily.

Good idea.

I'll put one in the Files area of the Yahoo Groups in just a minute.

Jason