On 2/15/07, Daniel Convissor <[EMAIL PROTECTED]> wrote:
> In the past, I've always used MySQL or Oracle, but mostly MySQL. Each
SQL
> distribution has its own peculiar ways of doing some things, and I know
that
> using some of the MySQL functions makes the code far easier to write and
> also opt
Jiju Thomas Mathew wrote:
> In general, good SQL is good SQL, no matter what the platform is.
True, but not every platform delivers the same results when sending it
good SQL.
David
Can you explain.. I got only exposure with MySQL..
--
Jiju Thomas Mathew
http://www.php-trivandru
> In general, good SQL is good SQL, no matter what the platform is.
True, but not every platform delivers the same results when sending it
good SQL.
David
Can you explain.. I got only exposure with MySQL..
--
Jiju Thomas Mathew
http://www.php-trivandrum.org
_
Daniel Convissor wrote:
> In general, good SQL is good SQL, no matter what the platform is.
True, but not every platform delivers the same results when sending it
good SQL.
David
___
New York PHP Community Talk Mailing List
http://lists.nyphp.org/ma
Hi Brian:
On Wed, Feb 14, 2007 at 10:19:09AM -0500, Brian Dailey wrote:
> different database backends without significant (or maybe any) changes to
> your code. Pear::DB seems to really do a good job with this. However...
The new PEAR MDB2 package does an even better job. Deals with building
s
Brian Dailey wrote:
A lot of the books and other material that I've been reading talk
about database abstraction - developing your application so that you
can use different database backends without significant (or maybe any)
changes to your code. Pear::DB seems to really do a good job with
th
Brian Dailey wrote:
A lot of the books and other material that I've been reading talk about
database abstraction - developing your application so that you can use
different database backends without significant (or maybe any) changes
to your code. Pear::DB seems to really do a good job with thi
Brian Dailey wrote:
So my question boils down to this: how does one balance writing code
that works regardless of the backend and still keep things optimized
for speed and clarity? Are there any generalized tips that any of you
can share from your experiences?
Don't forget to ask how portable
nswered by you doing a little research via
Google and testing out some of the available solutions to see what works
best for you.
-Tim
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Brian Dailey
Sent: Wednesday, February 14, 2007 10:19 AM
To: NYPHP
A lot of the books and other material that I've been reading talk about
database abstraction - developing your application so that you can use
different database backends without significant (or maybe any) changes to
your code. Pear::DB seems to really do a good job with this. However...
In the p
10 matches
Mail list logo
