Subject Re: [firebird-support] Newbie Qustion
Author Tony Blomfield
Kiaora.

Actually, I had FB1.5 in mind. We have pretty much reached the limit
oftuning with IB6 because the OPtimiser Sux big time. Im looking to get that
nice new Optimiser in FB working.

Must say Im not keen on swapping components. Thats a big job. This thing has
multiple components in the Web server, and Ive put a lot into learning IBX.
Also, I am pretty much against using 3rd party components for a variety of
reasons.

The rest sounds great.

I do have to look to the future though, and that will almost certainly be a
change to C#.NET and Vis Studio. Whats the situation then?









----- Original Message -----
From: "Helen Borrie" <helebor@...>
To: <firebird-support@yahoogroups.com>
Sent: Friday, July 25, 2003 4:32 PM
Subject: Re: [firebird-support] Newbie Qustion


>
> Hello Whangarei!!
>
> At 03:21 PM 25/07/2003 +1200, Tony Blomfield wrote:
> >I have an app developed in IB6 using IBX6.05
> >
> >Will this work seamlessly with FB? ie Is IBX fully compatible with FB?
> >
> >I wish to witch strategy from IB to FB.
> >
> >Tony.
>
> Seamlessly - probably, provided you stick with Firebird 1.0.x and
carefully
> test compatibility if you implement any Firebird-specific language
> features. For Firebird 1.5 and further down-track, you'd be well advised
> to plan on using IB Objects or FIBPlus, since Borland has indicated it has
> no intention of keeping IBX compatible with Firebird. Both of the
> Firebird-compliant component sets are technically superior to IBX, in any
case.
>
> On the transition from IB 6 to Firebird, the Firebird DSQL parser already
> spits the dummy on some bad SQL that IB 6 allows, so be prepared to
tighten
> up some of your joined sets and subqueries if you haven't been used to
> using fully-qualified column-names in your query specs to date.
>
> heLen
>
>
>
>
> To unsubscribe from this group, send an email to:
> firebird-support-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>