RE: [PEAR-DEV] SQL_* packages proposal
| From: | Rob Hutton | Date: | Sun, 14 Sep 2003 16:50:07 +0000 |
| Subject: | RE: [PEAR-DEV] SQL_* packages proposal | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21493@lists.php.net to get a copy of this message | ||
OK, sorry, missed that. I think for the docs/examples it would be good to
put a short description above each example like: "Aliasing join tables".
So the architecture is that you pass the SQL_Query object to a
SQL_Query_Renderer_* object to actually get the query string? I would then
recommend that the SQL_Query_Renderer be a factory class that generated an
object for the correct query renderer based on a parameter that can be
passed like the DSN is passed to DB and the correct backend object created.
Something like:
$query_renderer = SQL_Query_Renderer::factory('mysql');
This way, a map of the types of DBs to the correct backend is maintained in
the package, and the user doesn't need to worry about it.
One quick note on the Common class, all of the DBs that I have looked at,
the join has an "as" between the table and alias in the join clause....
If I could vote, it would definitely be a +1 ;-)
Thanks,
Rob
> -----Original Message-----
> From: Wolfram Kriesing [mailto:lists@kriesing.de]
> Sent: Sunday, September 14, 2003 11:30 AM
> To: Rob Hutton
> Cc: pear-dev
> Subject: Re: [PEAR-DEV] SQL_* packages proposal
>
>
> Rob Hutton wrote:
> > One simple thing to address, unless I am missing something, there is not
> > support in Join for aliasing.
>
> yes, there is
> please have a look in the comment for addJoin() here
> http://opensource.visionp.biz/SQL_Query_Join_php.138.0.html
>
> > Thanks,
> > Rob
> >
> >
> >>-----Original Message-----
> >>From: Wolfram Kriesing [mailto:lists@kriesing.de]
> >>Sent: Saturday, September 13, 2003 3:19 PM
> >>To: pear-dev
> >>Subject: [PEAR-DEV] SQL_* packages proposal
> >>
> >>
> >>i mentioned a while ago, that i was working on an SQL-abstraction
> >>package. Now i got something that i would like to propose.
> >>Its not to huge, but it works :-)
> >>Here are the packages and where to find them
> >>
> >>* SQL_Query
> >>http://opensource.visionp.biz/SQL_Query.110.0.html
> >>
> >>* SQL_Query_Renderer
>
> >>>>http://opensource.visionp.biz/SQL_Query_Renderer.140.0.html
> >>
> >>* SQL_Condition
> >>http://opensource.visionp.biz/SQL_Condition.143.0.html
> >>
> >>The packages are very well inline documented and provided with
> >>UnitTests. Actually all 3 packages are needed to make sense of the whole
> >>thing, so i think voting would need to be done once for all of them,
> >>once the naming is ok.
> >>
> >>
> >>btw. it also is the base for the 1.x version of the QueryTool
> >>
> >>--
> >>Wolfram
> >>
> >>http://opensource.visionp.de
> >>
> >>... authentication system ....
> >> http://sf.net/projects/auth
> >>
> >>--
> >>PEAR Development Mailing List (http://pear.php.net/)
> >>To unsubscribe, visit: http://www.php.net/unsub.php
> >>
> >>
> >
> >
> >
>
>
> --
> Wolfram
>
> http://opensource.visionp.de
>
> ... authentication system ....
> http://sf.net/projects/auth
>
>