New Question.
Is there a way to model one-many relationships with Acs Object Management?
Seems like a handy thing to be able to do.
I have no idea how that would work though...
You mean besides using a one_object_id_to_many_id_map table?
Just create a naturalnum attribute on your object without a corresponding form widget and reference this back to its parent object.
Any foreign key constraints have to be created separately in a SQL script.