Hi Jason,
Metabase is a library that tries to hide 99% of the differences between all
databases. In that sense
it is a thick abstraction layer.
The other school of thought is to provide a thin layer that doesn't do very
much so that it runs fast.
I am the author of another database abstraction library, ADODB
(http://php.weblogs.com/adodb)
that leans more towards that school. PEAR's DB is a similar thin layer.
You have to decide on your needs based on
1. What do you want: speed or flexibility -- remember flexibility also means
increased complexity.
2. Are you using a database abstraction layer as an insurance policy
(changing databases)?
If so then just choose the one that provides you an easier upgrade path.
John Lim
PS: ADODB is modelled on Microsoft's ADO, so it's popular among converted
ASP programmers. If you
one of these people, ADODB might be attractive to you.
"Jason Lotito" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Looking into Database Abstraction, and I was recommended to Metabase. I
> have looked over it, and found that I like it. However, I was looking to
> gain further insight as to other people using Metabase, and their
> experiences with it, good, bad, problems, no problems, etc.
>
> Thank you
>
> Jason Lotito
> www.NewbieNetwork.net
> Where those who can, teach;
> and those who can, learn.
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
