--- In IBObjects@yahoogroups.com, "Paul Hope" <paulhope@...> wrote:

>
> > At 09:43 PM 16/02/2007, you wrote:
> > >Unfortunately I have lots of code like
> > >Select a.bla,b.bla,c.bla
> > >from (taba a join tabb b)left outer join tabc c
> > >
> > >The presence of these brackets breaks the parser. I know
> > Helen has told me
> > >that the use of brackets in the 'from' is 'not correct syntax'

but I

> > >have been using it for years, it worked in V4.3Aa and it is
> > accepted by
> > >the engine.
> > >
> > >I have a huge task getting rid of the brackets especially as
> > a lot of
> > >SQL is generated in code and it is sometimes difficult to
> > see both ends
> > >of the brackets.
> > >
> > >Should the parser be 'fixed' or are we officially declaring
> > the use of
> > >brackets in 'from' illegal?
> >
> > Brackets in 'from' are legal, just not the way you are using
> > them. You can (and sometimes need to) bracket the join
> > conditions, i.e.
> >
> > from tableA a
> > join tableB b on (........)
> >
> > I'm curious about where you picked up the idea of bracketing
> > everything including the ON .... It's not even provided as
> > an optional syntax under the standard, as far I can find out...
> >
> > Helen
>
> Yes, I'm curious as well. Its so long ago I don't remember. I've

never

> read the standard my guess is I saw it somewhere :-/
>
> Paul
>

I am concerned about the wider implications - regardless of
the 'correctness' of syntax used in earlier versions.

It seems each new release, instead of building on previous ones,
creates new problems in existing, tested and released code.

We have evaluated IBObjects and are seriously considering
incorporating it into our products but we are very concerned about
configuration control and backward compatibility. From messages in
this forum, upgrading seems a somewhat risky business, especially if
considering migrating to Firebird 2.0 from 1.5.

Clients / Users know nothing of IBObjects, (nor should they). All
they will see is an application that used to work that now has
problems after a routine maintenance upgrade. This will reflect badly
on us. The only way to avoid these client problems will be to revisit
all old test scripts from scratch, adding to the admin overhead and
associated costs. There is also no telling what impact there may be
on user support documentation.

It is a problem for us and we will monitor the situation before
making a final decision.

I would welcome any comments or assurances in this area.

George