-
Jean-Paul Smets authored
There is no reason not to support sql_catalog_raise_error_on_uid_check for both cases of UID inconsistency. UID change happens for example with inconsistent catalog and ZODB after disaster recovery. It can be useful to prevent raise during a double catalogin of the database after a disaster recovery. Else, it is just impossible to recover.
94bedc0a
Name |
Last commit
|
Last update |
---|---|---|
bt5 | ||
erp5 | ||
product | ||
slapos | ||
tests | ||
.gitignore | ||
CHANGES.erp5.util.txt | ||
MANIFEST.in | ||
README.erp5.util.txt | ||
setup.py |