Hi Koen, > You cannot do this with a many to many relation. In this case you could > explicitly map the join table and use 2 many to one relations.
Before ManyToMany: CONSTRAINT users_has_projects_pkey PRIMARY KEY (users_id, projects_id) After ManyToOne: CONSTRAINT users_has_projects_pkey PRIMARY KEY (id) Before it got better, because there was no id and version and the primary keys were correct (users_id, projects_id). Now is not exactly correct, but I can create additional fields automatically. I will remove id and version and change the primary keys directly in PostgreSQL. The ideal would be able to perform operations to changes tables after created: ADD COLUMN, DROP COLUMN, TYPE, RENAME COLUMN, RENAME, etc http://www.postgresql.org/docs/current/static/sql-altertable.html > Or propose a workable syntax to extend dbo? (when I understand more about the Wt, I'll try to help) Tks John ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
