Subject | RE: [ib-support] Firebird and the BDE/SQL Links |
---|---|
Author | pschmidt@interlog.com |
Post date | 2002-10-10T13:55:17Z |
On 9 Oct 2002 at 18:22, Ann W. Harrison wrote:
the release notes, a notice that Dialect 1 is depreciated, and that it is no longer
being maintained. For FB 2.0 the SET DIALECT statement should be syntax
checked but ignored and the engine hard wired to Dialect 3. As the code
maintainers, doing other things find Dialect 1 only code, they can then clean it out.
One of the issues currently being dealt with, is running two engines at the same
time, so there would be nothing wrong with running FB 1.0 for the dialect 1
databases, and FB 2.0 for the Dialect 3 databases. So the issue of maintaining
Dialect 1 for all future engines becomes, really a non-issue.
Paul
formerly paul@...
> At 10:22 PM 10/9/2002 +1000, Alan McDonald wrote:Can I add my 1.2342 cents (2 cents CAD), I think that for FB 1.5 there should be in
> >What is the cost of maintaining dialect 1 connectivity? Isn't it more work
> >to remove it than to leave it go for some time?
>
> I agree with Alan here - we should leave dialect 1 available
> but
>
> 1) Don't add it to new interfaces (e.g. JBird)
> 2) Don't add features to it (e.g new datatypes)
> 3) Do encourage people to move away from BDE
>
the release notes, a notice that Dialect 1 is depreciated, and that it is no longer
being maintained. For FB 2.0 the SET DIALECT statement should be syntax
checked but ignored and the engine hard wired to Dialect 3. As the code
maintainers, doing other things find Dialect 1 only code, they can then clean it out.
One of the issues currently being dealt with, is running two engines at the same
time, so there would be nothing wrong with running FB 1.0 for the dialect 1
databases, and FB 2.0 for the Dialect 3 databases. So the issue of maintaining
Dialect 1 for all future engines becomes, really a non-issue.
Paul
formerly paul@...