Re: [PHP-DB] Abstraction layer or not?
> > I'm working on a new site, and I'm wondering whether to use an > > abstraction layer or not. I don't have any plans to switch DB system, > > but you never know what the future holds. I figure that there's no > > reason not to, but are there any down sides? Which abstraction layers > > are good? well, any down side ? may be slower for example. So, if you don't plan to switch db system, the speed of the layer could be your criteria. > ADOdb is a good one. PEAR also has an abstraction class. Once you get > used to using them, they make things easier over all. I've never > actually switched databases with them, so I don't know how much easier > it makes that. I find them ideal for error catching and reporting. I agreed. ADOdb (http://php.weblogs.com/ADODB) is quite nice, fast, (the fatest ?) and very helpful even if you don't change db. See benchmark at http://phplens.com/lens/adodb/. Well, it's from adodb, may be you would find an other one written by those using pear_db. Regards, Philippe -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DB] Abstraction layer or not?
Yeah, and what is a DB wrapper but a type of abstraction layer, right?? I'd prefer that people use one that's already developed and documented then trying to write their own. Of course, if you never share your code, then do what you want. ---John Holmes. -Original Message- From: Leif K-Brooks [mailto:eurleif@;buyer-brokerage.com] Sent: Tuesday, November 05, 2002 9:28 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [PHP-DB] Abstraction layer or not? True, but a DB wrapper can do the error reporting as well. John W. Holmes wrote: I'm working on a new site, and I'm wondering whether to use an abstraction layer or not. I don't have any plans to switch DB system, but you never know what the future holds. I figure that there's no reason not to, but are there any down sides? Which abstraction layers are good? ADOdb is a good one. PEAR also has an abstraction class. Once you get used to using them, they make things easier over all. I've never actually switched databases with them, so I don't know how much easier it makes that. I find them ideal for error catching and reporting. ---John Holmes... -- The above message is encrypted with double rot13 encoding. Any unauthorized attempt to decrypt it will be prosecuted to the full extent of the law.
Re: [PHP-DB] Abstraction layer or not?
True, but a DB wrapper can do the error reporting as well. John W. Holmes wrote: I'm working on a new site, and I'm wondering whether to use an abstraction layer or not. I don't have any plans to switch DB system, but you never know what the future holds. I figure that there's no reason not to, but are there any down sides? Which abstraction layers are good? ADOdb is a good one. PEAR also has an abstraction class. Once you get used to using them, they make things easier over all. I've never actually switched databases with them, so I don't know how much easier it makes that. I find them ideal for error catching and reporting. ---John Holmes... -- The above message is encrypted with double rot13 encoding. Any unauthorized attempt to decrypt it will be prosecuted to the full extent of the law.
RE: [PHP-DB] Abstraction layer or not?
> I'm working on a new site, and I'm wondering whether to use an > abstraction layer or not. I don't have any plans to switch DB system, > but you never know what the future holds. I figure that there's no > reason not to, but are there any down sides? Which abstraction layers > are good? ADOdb is a good one. PEAR also has an abstraction class. Once you get used to using them, they make things easier over all. I've never actually switched databases with them, so I don't know how much easier it makes that. I find them ideal for error catching and reporting. ---John Holmes... -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DB] Abstraction layer or not?
I'm working on a new site, and I'm wondering whether to use an abstraction layer or not. I don't have any plans to switch DB system, but you never know what the future holds. I figure that there's no reason not to, but are there any down sides? Which abstraction layers are good? -- The above message is encrypted with double rot13 encoding. Any unauthorized attempt to decrypt it will be prosecuted to the full extent of the law. -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
