Re: OO -> RDBMS mapping

Andi Gutmans wrote:

Hmm I'm not quite sure.JDO includes mapping of class hierarchies to RDBMS,

not sure how that would work - can you give an example? (or url) .. dataobjects forces you to make a class for each table, - so making one class extend another table... should be possible.

transaction management (including locking)

this could be added, without too much work.. (seems like a good addition)

and OQL,

mmh, thats a new abbreviation to me :)

a simple query language pretty much the most simple parts of SQL in order to retrieve the objects you want to work on.

Thats sounds like quite an overhead.. - both for the class and the user (to learn).. just letting them do raw SQL $object->query().. kind of solves that. (although it obviously has the catch of breaking the database independance) Regards Alan

Andi At 10:19 AM 11/1/2002 +0100, Lukas Smith wrote: From: Andi Gutmans [mailto:andi@zend.com] Sent: Friday, November 01, 2002 10:14 AM To: pear-dev@lists.php.net Subject: [PEAR-DEV] OO -> RDBMS mapping Hi, Has there been any talk on developing something similar to JDO (Java

Data

Objects) in PEAR? I think it'd be a very interesting thing for PHP. It is often much

easier

to fetch database objects, change them and commit than using SQL. Andi

Hi, DB_Object is probably what you are talking about: http://pear.php.net/package-info.php?pacid=80 regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de