RapidDataMapper, a new Object-Relational-Mapper

[eluser]m4rw3r[/eluser]
@all:

The second part of two of the quick start guide is done: http://rapiddatamapper.com/forum/viewtop...t=3&p=5#p2.

It is very simple, and shows how little code is needed to interact with the database

@BrianDHall:

Yes, that is one of the strengths of RDM, the ability to change all the defaults of the mappers (without losing performance too!) to whatever you like. You can also create new descriptors which contain your own default class -> singular -> table conversion algorithms (the same goes for columns, relations and primary keys).

About creating a sample app; I've made a simple (and dirty) quick start app here: http://rapiddatamapper.com/forum/viewtopic.php?f=6&t=3.

But I'm also going to resume my involvement in Ionize, and we'll see if I use RDM there (probably a gradual change, I need to restructure the template parser usage too).

@ben_co:

Bulk updates and delete are not really implemented, but if an object is changed, then all the related objects will also be saved if they have been modified (depends on the relation type).
So it is not really a fully working bulk update.
(But I have planned a bit on making it, when I've decided how to implement the Unit of Work handler (I think I can try to create some nice algorithm for creating the least number of queries (for update/insert), but some help with that would be nice )

Deletes of related objects will be supported (and I will probably also see to it that updates always propagates to the related objects), with the Db_Descriptor->setOnDeleteAction method (it is implemented, but not the logic behind it).

About multi DBMS-support, it is supported, the problem is that RDM only has one driver: MySQL