DataMapper ORM v1.8.0

[eluser]WanWizard[/eluser]
[quote author="Chillahan" date="1305913425"]Would you recommend against just forking DM and changing the id throughout to be id OR tablename_id? I guess it probably isn't so easy, there's a LOT of code there[/quote]
It's going to be quite a job, as it requires changes throughout the code, but also to the relationship definitions (which also append '_id' to any foreign key you define). I've already started on this, but it's going to take a while.

I am confused - I thought the CI transaction did allow for grouping of operations? I am talking about multiple operations in one shot, btw, not across server requests. Just if I want to be sure a new record gets added to three tables, or none.

What I mean is that Datamapper allows you to enable transactions internally for it's database operations. That means that within the Datamapper method, the database call is wrapped in a transaction.[/quote]

If you do it manually, using the method documented here, it's not a problem as these are direct mappings to CI's transaction method ( so $object->trans_start() is identical to $this->db->trans_start() ). Sorry if my remark confused you.

Foreign keys should not be defined NOT NULL, as there are situation where Datamapper explicitly sets them to NULL, for example when deleting relations. If you use a DEFAULT value, you run the risk of creating a false relation. Using zero instead of NULL is relatively safe, unless zero is a valid 'id' value.