Take a look to a new Firebird 2.1 next month and probably you will change
your idea about it...
UDF: FreeAdHocUDF, a lot of internal SQL function...
and if you wanna a good book www.ibphoenix.com Helen Borrie book... a MUST!


Codebue Fabio
.-----------------------------.
  _ \       __|       _||
  __/____|\__ \  _ \  _| _|
 _|       ____/\___/_| \__|

P-Soft di Codebue Fabio & C. sas
via B.Storti, 19
24060 - Chiuduno - BG
Italy
Phone: +39.030.839435
Fax: +39.030.5100306
Mobile: +39.348.3515786
.-----------------------------.
Web  : www.p-soft.biz
EMail: [EMAIL PROTECTED]  

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt Emson
Sent: Wednesday, April 09, 2008 12:48 PM
To: FPC-Pascal users discussions
Subject: Re: [fpc-pascal] Looking for a Firebird book?

Michael Van Canneyt wrote:
> Strange that you say this. We have firebird databases in production at 
> more than a thousand sites, ranging from simple desktop installations to
> sites with more than 500 simultaneous users. Firebird didn't fail on
> us once.

Interbase 7.1 and 7.5 were very bad. Interbase 6 was poor.

Firebird 1.x was bad. We stopped using Firebird when the compatibility 
was lost. Like I said, Firebird was bad last time I used it - Interbase 
was awful in the 2 and a half years I used it. Guilt by association? ;-)

UDF was biggest issue. The database relied heavily on using custom UDF 
functions, as well as the greater amount of FreeUDFLib. It also tried to 
do *everything* in stored procs, which is a really bad idea IMHO. A 
server process would have solved a lot of the instanility, which were 
caused mostly by implied logical second tier issues due to the design 
mentioned above.

_______________________________________________
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

_______________________________________________
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Reply via email to