[Phplogcon-dev] Database abstraction layer for phpLogCon

[Rainer Gerhards]

Brian,

please let me elaborate why I proposed some time ago to use a different
db abstraction layer. Just so that we remember the reasoning.

The db abstraction layer we have done works, but is a bit "rough" and
also limits the abilities to use SQL to its full extent. At least this
is what has been discussed so far. My hopes for a layer like Pear is
that it provides a higher-level abstraction with better functionality.
So my main objective behind that would not be to support additional
databases (although this definitely is a secondary goal) but to have
cleaner and more capable code inside phpLogCon. In the light of this,
I'd propose to not support MSSQL and MySQL natively, because that would
require us to continue to use our own layer, which seems to have some
issues.

Of course, the question is what implications Pear has - e.g.
performance-wise.

I hope this clarifies and initiates another round of good discussions ;)

Rainer 

> -----Original Message-----
> From: phplogcon-dev-bounces at lists.adiscon.com 
> [mailto:phplogcon-dev-bounces at lists.adiscon.com] On Behalf Of 
> Brian Shea
> Sent: Tuesday, December 06, 2005 6:37 PM
> To: phplogcon-dev at lists.adiscon.com
> Subject: Re: [Phplogcon-dev] Database abstraction layer for phpLogCon
> 
> The Pear DB sounds good, i have the pear lib installed and 
> have used it
> before. I can modify the session handlers to include pear 
> support. It would
> be a good idea to have native support for mssql/mysql for 
> those that can't
> use pear. I think those two are probably the most widely used DBs. All
> other's can be supported by pear.
> 
>  That item has been added to the TODO list.
> 
> 
> On 12/6/05, Michael Meckelein <mmeckelein at hq.adiscon.com> wrote:
> >
> > Hi,
> >
> > I will discuss each topic in a separate email on the list. 
> I think it is
> > easier for tracking.
> >
> > One of the most desired items for phpLogCon is a database 
> abstraction
> > layer. We have already implemented our own db abstraction 
> layer, but it
> > is more or less an 'it does, but it not perfect' one (also it only
> > supports mysql, mssql and access).
> >
> > We had often trouble to get all supported database working. 
> Therefore we
> > have considered to use a third party db abstraction layer 
> like pear:db
> > [1] or adodb for phpLogCon.
> >
> > Brian, as you mentioned, the session handler only works 
> with mysql. If
> > we want support other db we have to write a wrapper. Maybe 
> it is a good
> > time to implement the third party stuff now in order to get 
> rid of all
> > the trouble with different db.
> >
> > Brian, how does it sound? Maybe you have already experience 
> with db:pear
> > or adodb? I have already tested both in smaller projects. I 
> personally
> > prefer db:pear, but both are powerful and easy to use.
> >
> > [1] pear::db
> > http://pear.php.net/package/DB
> > [2] ADOdb
> > http://adodb.sourceforge.net/
> >
> > Best Regards,
> > Michael
> > _______________________________________________
> > Phplogcon-dev mailing list
> > http://lists.adiscon.net/mailman/listinfo/phplogcon-dev
> >
> _______________________________________________
> Phplogcon-dev mailing list
> http://lists.adiscon.net/mailman/listinfo/phplogcon-dev
>