You could simply use like doctrine DBAL or an already existing one made specially for ORM, or you can design one and at the moment make it to use only MySQL PDO is actually good enough to do that, I know that the only thing I had to do in my ORM was to write a special class to translate some queries for MySQL (to be able to use LIMIT for objects instead of rows). On 17 June 2011 12:06, 李白|字一日 <calidion@xxxxxxxxx> wrote: > thanks, how about the abstraction of different databases? > it seems PDO is still lack of functions of importance. > > I'm currently trying to design a automated model like django or > activeRecord. > it should be quiet simple and automated, > i have managed to possibly create the whole database only once. > but the abstraction of the database and subsequent manipulation seem far > more complicated than the previous part > > i'm currently only support mysql and only support whole query at once. > > 2011/6/17 jean-baptiste verrey <jeanbaptiste.verrey@xxxxxxxxx> > >> - defining the mapping schema in an alternate method than using meta data >> (I HATE them, I would prefer an XML file with a DTD so you could use >> autocompletion with IDE like NetBeans) > > > java's hibernate instead of python's exlir or ruby 's rail style ? mean no > ActiveRecord? > > >> - clear keywords in the schema >> > > >> - OQL can do UPDATEs >> > > - one and only one configuration file with everything in it (and with why >> not the schema) >> > > - to not forget to KEEP IT SIMPLE, specialised ORM that does everything >> already exists so there's no point in writing one! >> >> that's it for me (at least at the moment) >> >> Of course I would suggest to use PHP 5.3 specially for late static binding >> (and for people that love namespaces) >> > > > >> > >> >> On 17 June 2011 07:42, 李白|字一日 <calidion@xxxxxxxxx> wrote: >> >>> and how to design such an orm in current state of php language? >>> >> >> >
