Bug with archivable and auto_add_pk as default behaviors

Open nothingisdead opened this issue 12 years ago • 1 comments

It looks like if you add archivable and auto_add_pk as default behaviors to build.properties, you have to list them with auto_add_pk first, as follows:

propel.behavior.default = auto_add_pk, archivable,...

If you list them in the following order:

propel.behavior.default = archivable, auto_add_pk,...

The id field of the *_archive tables is created with AUTO_INCREMENT setting, preventing archived records from being inserted, since the archive method explicitly inserts the primary key.

Jul 15 '13 02:07 nothingisdead

Just had the same problem.

Jul 29 '16 15:07 TheKnarf