05-30-2008, 08:08 PM
|
#1 (permalink)
|
|
is cute and cuddly
Join Date: Mar 2008
Location: Vegas, Baby
Posts: 963
Thanks: 31
|
To abstract, or not to...
So I just ran into another snag. I've been developing a small group of classes that all use mysqli. After two weeks of work on my local test server, I uploaded them to my host to put em online to show off, and.... my host doesn't have mysqli, it's mysql or bust.
Not only do I hate them because for such a large company they barely offer more than a skeleton server, but I also hate them because they brought it to my attention that my scripts aren't very backwards compatible at all.
So now I want to create a very very basic abstraction. I'm thinking two classes, both sadly just reproducing the same methods the mysqli object uses, but one which would use mysql functions if that extension isn't loaded on the server. At first I thought this would be a good chance to play with abstract classes, but I dunno.
Any ideas for how to go about this? I basically want something in the background to check function_exists('mysqli') and use one of two possible sets of methods based on that knowledge. Maybe it'd just be easier to release two versions of this entire thing, one based on mysqli, one on mysql heh...
-m
|
|
|
|