Subject | Re: Optimal settings |
---|---|
Author | Alexander V.Nevsky |
Post date | 2004-05-07T10:01:11Z |
--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:
themselves are the same but result will be different if numerics or
dates are used because of different underlying types. The only namely
commands differences I know are
a) Ambiguity checking is not forced in dialect 1 (I regret)
b) In dialect 1 you can
create procedure testconc(a char(5), b char(5))
returns (c char(10))
as
begin
c=a+b;
suspend;
end
select * from testconc('2','3')
C
==========
5.0000000
in dialect 3 you can't do this. Thank Goodness. It is one of most
guileful and hard to find mistakes I know.
Best regards,
Alexander
wrote:
> I use both and I've never struck a situation where an SQL commandworks in
> one and not the other - maybe I'm boringI'm not closely familiar with dialect 3 and supposed SQL statements
themselves are the same but result will be different if numerics or
dates are used because of different underlying types. The only namely
commands differences I know are
a) Ambiguity checking is not forced in dialect 1 (I regret)
b) In dialect 1 you can
create procedure testconc(a char(5), b char(5))
returns (c char(10))
as
begin
c=a+b;
suspend;
end
select * from testconc('2','3')
C
==========
5.0000000
in dialect 3 you can't do this. Thank Goodness. It is one of most
guileful and hard to find mistakes I know.
Best regards,
Alexander