propelorm/Propel — Issue #247: versionnable and archivable
Author: kigeia
Created: 2012-01-01 13:35:21+00:00
State: open

Hi, I've got an object that is versionnable and also got the soft_deleve behavior. When upgrading soft_delete to archivable, the generated code throws a BaseObject Exception.
It makes sense that when you got a versionnable behavior, you don't need an extra achive table to store the deleted objects.
So the main issue here would be to add an option to the versionning in order to disable the cascade delete of version objects (and add a log_deleted_at column to the version table).

Any clues on this Issue ?

Bye

Joss