RE: [PEAR-DEV] LDAP DB class
| From: | Lukas Smith | Date: | Tue, 08 Jan 2002 16:14:48 +0000 |
| Subject: | RE: [PEAR-DEV] LDAP DB class | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3833@lists.php.net to get a copy of this message | ||
Well I must admit I know more about Metabase than about PEAR DB.
There is an effort to mere the two projects (which you can read up on in
the archive in case you are interested)
I was planning on writing an LDAP DB abstraction for Metabase (or the
merged version). But I currently do not even have a running LDAP server
here at work nor do I the time to dive into LDAP.
So I will ask a few more general question:
My Goal was to write an layer that would allow me to very simply switch
between an LDAP and an RDBMS to store my userdata.
I did not want to have do change any of my code that would sit on top of
this layer. From you implementation from simpleQuery() I see that you
are definitely changing the interface ... could this not also be hidden
underneath the layer?
I guess this would mean actually working off of an SQL query and parsing
that to extract the parameters you need (like action etc) => leads to
overhead
The question is obviously if this is even feasible.
I was not sure of this myself so alternatively I was thinking of writing
a class that would handle my user manipulations and that would build the
"queries" as SQL queries or as LDAP queries.
What do you think?
Best regards,
Lukas Smith
smith@dybnet.de
_______________________________
DybNet Internet Solutions GbR
Alt Moabit 89
10559 Berlin
Germany
Tel. : +49 30 83 22 50 00
Fax : +49 30 83 22 50 07
www.dybnet.de info@dybnet.de
_______________________________
> -----Original Message-----
> From: Ludovico Magnocavallo [mailto:ludo@sumatrasolutions.com]
> Sent: Tuesday, January 08, 2002 4:54 PM
> To: Lukas Smith
> Subject: Re: [PEAR-DEV] LDAP DB class
>
> Hi Lukas,
> thanks for the feedback =)
>
> The implementation is tentative, as many SQL features are not easily
> implemented, or require workarounds in LDAP. Please let me know if you
> need
> explanations on the class use, or if you think of changes to the
class.
>
> Ludo
>
> ----- Original Message -----
> From: "Lukas Smith" <smith@dybnet.de>
> To: "'Ludovico Magnocavallo'" <ludo@sumatrasolutions.com>;
> <pear-dev@lists.php.net>
> Sent: Tuesday, January 08, 2002 4:37 PM
> Subject: RE: [PEAR-DEV] LDAP DB class
>
>
> > This is very exciting.
> > I was planning on working on something like this as well but I
haven't
> > had the time do start yet (I am still a newbie when it comes to
LDAP).
> >
> > I will look over it soon (hopefully).
> >
> > Best regards,
> > Lukas Smith
> > smith@dybnet.de
> > _______________________________
> > DybNet Internet Solutions GbR
> > Alt Moabit 89
> > 10559 Berlin
> > Germany
> > Tel. : +49 30 83 22 50 00
> > Fax : +49 30 83 22 50 07
> > www.dybnet.de info@dybnet.de
> > _______________________________
> >
> > > -----Original Message-----
> > > From: Ludovico Magnocavallo [mailto:ludo@sumatrasolutions.com]
> > > Sent: Tuesday, January 08, 2002 4:32 PM
> > > To: pear-dev@lists.php.net
> > > Subject: [PEAR-DEV] LDAP DB class
> > >
> > > I have written a tentative implementation of a DB class to connect
to
> > LDAP
> > > servers. It's still pretty rough, misses almost all comments, and
> > needs a
> > > lot of testing (I only tested it in anonymous mode).
> > >
> > > Is anybody interested in commenting on its usefulness, and its
design?
> > >
> > > Ludo
> > >
> >
> >
> >