While MySQL is a very nice and fast db not everyone in
the world uses it (yet).
It would be a nice thing to support multiple databases
through an abstraction layer that removes all db work
from the various classes and centralizes it into a
sigle class. this would allow a module to simple call:
This is different from simple PEAR or PHPLIB db
abstraction at the db interface level, as we're
abstracting all of our application level db interaction.
This is a very large and time intensive project that
requires knowledge of multiple databses and a great
deal of planning to make a fast, useable and scaleable
API. This is not something to be undertaken in an
In terms of scheduling there are two schools of thought:
- Incorperate it now fo rlots of testing and less
porting work later.
- Do this last once all the db queires, schems and such
take place and we're not trying to abstract a moving
My personal feeling is that there is a great deal of
work to do in the phpslash feature set and some
confusion about where is is going. Until these things
settle down and a concrete feature set is devloped with
a fintie direction, such a large and invaseive task
should not be undertaken
Log in to post a comment.