On Sunday, October 14, 2001, at 08:41 AM, Sterin, Ilya wrote:
> > >> -----Original Message----- >> From: Terrence Brannon [mailto:[EMAIL PROTECTED]] >> Sent: Sunday, October 14, 2001 10:38 AM >> To: [EMAIL PROTECTED] >> Cc: [EMAIL PROTECTED] >> Subject: Re: Postgres w/DBI >> >> >> >> On Sunday, October 14, 2001, at 07:25 AM, [EMAIL PROTECTED] wrote: >> >>> Hello All, >>> >>> We've been using MySQL with Perl/DBI for quiet awhile, and have been >>> looking at >>> trying Postgres. I was wonder how much re-coding is involved if we use >>> our >>> existing scripts with Postgres instead of MySQL?? >> >> There are a few answers to your question >> >> 1 - there do exist powerful database-independent SQL generators for >> Perl. namely, DBIx::Recordset and Alzabo, both at search.cpan.org > > Right but DBI is also database independent in most cases. Yes you can > have > db specific commands with func() and some attributes, but if you > exercise > proper portable coding then there shouldn't be any problems. > DBI may be independent, but the fact that it does nothing with the SQL that is sent to the database and the fact that SQL varies from vendor to vendor means that there are database compatibility issues in SQL that are not and should not be handled by DBI but must be handled by a layer on top of DBI. I tire of stating this and I wonder why people want to gloss over this glaringly obvious fact: SQL varies from vendor to vendor.
