Subject Re: [IBDI] Re: Porting from MS SQL Server 7.0 to Interbase
Author Marc Spitzer
----- Original Message -----
From: <johnlim@...>
To: <IBDI@egroups.com>
Sent: Sunday, 25. June 2000 0:43
Subject: [IBDI] Re: Porting from MS SQL Server 7.0 to Interbase


> Dear Claudio,
>
> Thanks for the invite to the new IB-Conversions emailing list
> and the fast response to the email.
>
> >
> > > 3. Interbase uses || for string concat, SQL Server uses +.
> >
> > Interbase is ANSI-SQL almost completely. As always, uncle Gates
> prefers to
> > use his "enhanced" versions
>
> Thats true -- but we have to ask ourselves this -- is the aim of
> Interbase to be the "purest" database, or make it easy so that the
> more people join up, the better. I'd like to point out that Oracle
> and Sybase also support "+".

Well work just sent me to the Oracle intro to sql/plsql course and for
concatenation we used the || operator and the concatenation function, for
1 example. I did not see the + sign anywhere except for addition and
left outer join. And personally I prefer having 1 way to do it, its
simpler.
Why add confusion to the product? For example in the proposed mysql
mode will Interbase support transactions, mysql does not. And if you
do how much compatibility do you give up with mysql?

My personal opinion is that the real hard part of databases is getting
the data model/design correct. That is what will make or break you,
the rest you can do with the manual open while coding fairly well. I
am not saying that you can just jump in and code a great application
without any experience in your database, but with a good enough data
model you should be able to code a good one and then make it great
as you get experience.

marc spitzer

>
> I think that the new Open Source Interbase initiative is excellent --
> it is attracting developers like me who wouldn't have considered it 6
> months ago. And the easier it is to port to Interbase the better!
>
> The new dialect approach is a very good idea. I would suggest a
> dialect for MS Access/SQLServer compatibility. If Interbase had 90%
> compatibility with MS Access and had a Access Upsizing Wizard,
> Interbase would convert lots of users when Access started to have
> scaling problems.
>
> Currently Access users are going for MS SQL Server when they hit
> scaling problems.
>
> Similarly, a MySQL compat mode would do wonders to Interbase's market
> share.
>
> Forget Oracle, Sybase, Informix -- the market share is too small and
> if you prepared to pay those prices, they wouldn't be interested in
> Interbase in the first place.
>
>
> > > Will the collation kit support Visual C++? We don't own a copy of
> > > Borland C++.
> >
> > IB itself is compiled with MS product in the Windows platform
>
> This is proof that Microsoft is too dominant for its own good! Even a
> borland product uses MS Visual C++!
>
> Regards, John Lim
>
>
> ------------------------------------------------------------------------
> IT Professionals: Match your unique skills with the best IT projects at
> http://click.egroups.com/1/3381/5/_/679568/_/961908243/
> ------------------------------------------------------------------------
>
> Community email addresses:
> Post message: IBDI@onelist.com
> Subscribe: IBDI-subscribe@onelist.com
> Unsubscribe: IBDI-unsubscribe@onelist.com
> List owner: IBDI-owner@onelist.com
>
> Shortcut URL to this page:
> http://www.onelist.com/community/IBDI
>
>