Subject | Re: [firebird-support] Re: Firebird 2.0 and EXECUTE BLOCK |
---|---|
Author | Helen Borrie |
Post date | 2006-02-22T18:17:19Z |
At 04:05 AM 23/02/2006, you wrote:
another forum, too. Please would you read the General Notes section
at the beginning of the Firebird 2 beta 2 release notes.
When considering tools to support betas, bear in mind that
third-party tools developers aren't very like to make production
releases supporting features which might change. That's inherent
when using betas with 3rd-party tools that were built for the current
release version.
Betas are for field-testing and it's not usually very helpful if
field-testers don't use the native tools for tests.
On the other side of the coin, the tools developers are usually very
interested to get feedback in their own forums about how *their*
products work with the oncoming betas, since they are sure to be in a
beta cycle of their own...
^ heLen
> > For one thing, Database Workbench does not yet like this :-)Actually, any questions about Firebird 2 betas are questions for
> >
> > Although it supports all other Firebird 2 PSQL features, it does
>not
> > yet support "execute block".
> >
> > Martijn Tonies
> > Database Workbench - development tool for Firebird and more!
> > Upscene Productions
> > http://www.upscene.com
> > My thoughts:
> > http://blog.upscene.com/martijn/
> > Database development questions? Check the forum!
> > http://www.databasedevelopmentforum.com
> >
>
>Ah, well that will help explain my confusion as well :) OK, then i
>can 'fall back' to the good ol' ISQL client for testing this then.
>
>Of course, you know that my next question will be 'when will this
>support be ready?', but I'll hold off for now, and besides, that's a
>question for another forum anyway.
another forum, too. Please would you read the General Notes section
at the beginning of the Firebird 2 beta 2 release notes.
When considering tools to support betas, bear in mind that
third-party tools developers aren't very like to make production
releases supporting features which might change. That's inherent
when using betas with 3rd-party tools that were built for the current
release version.
Betas are for field-testing and it's not usually very helpful if
field-testers don't use the native tools for tests.
On the other side of the coin, the tools developers are usually very
interested to get feedback in their own forums about how *their*
products work with the oncoming betas, since they are sure to be in a
beta cycle of their own...
^ heLen