Thanks Helen for the clear document.

Jason

Coming back to my original point and your recognition that the latest
version inflicts some significant migration pain it would be very helpful if
error reporting on these issues could be more specific. I'm making the
assumption here that your SQL parsing will recognise these things and could
report them without a massive amount of effort.

For example my explicit join brackets returned an error 'column unknown'
which was unrelated. My wrong dialect in the upgraded ib_connection caused
an access violation. Missing aliases are not reported. Use of table names
and not aliases in keylinks etc is not reported. Also the error doesn't
tell you which object contains the SQL in error.

Feasible/appropriate?

Regards
Paul

> Helen,
>
> Yes, you precisely understand. Even with Firebird 1.5 and
> all other Interbase, etc. relation alias is now the standard
> when they are used. If I don't get them from the server I
> parse them out of the SQL. That's why this required a lot
> more work now than I anticipated because I wanted to keep
> everything uniform. Having it the defacto way for things to
> be handled makes for a little bit (I know, for some a lot) of
> migration pain but then this is a dead issue and I won't have
> to carry the overhead of it being any other way. It's a
> judgment call I made with the long-term consistency and
> health of the product.
>
> Obviously I didn't make this as clear as I should have
> because you never seem to miss a beat. I'm glad we are
> resolving this.
>
> Regards,
> Jason
>
>
> >
> > At 08:37 AM 24/02/2007, Jason wrote:
> > >Helen,
> > >
> > > > http://www.ibobjects.com/docs/IBO_47_Migration.pdf
> > >
> > >Please be sure to include mention of the need to change
> > property settings
> > >from table names to relation alias names when they are used.
> > For example,
> > >if a query were:
> > >
> > > select a.mycol1, a.mycol2
> > > from mytable a
> > >
> > >The Keylinks would have to be changed from:
> > >
> > > MYTABLE.MYCOL1
> > >
> > >to:
> > >
> > > A.MYCOL1
> > >
> > >
> > >If a relation alias is used it must now be used in all the
> > property settings
> > >of IBO.
> >
> > OK, I have added that but I'm not certain that it is wholly
> correct.
> > Are you saying that you have made this general, regardless
> of the ODS
> > of the database the app is connecting to? i.e. that IBO needs the
> > aliases, even if the SPB does not return the alias?
> >
> > Helen
>
>