[REF] porting to new api
[IMP] removing 'FOR UPDATE NOWAIT' as ROW EXCLUSIVE lock is already acquired by DELETE and INSERT
http://www.postgresql.org/docs/9.2/static/explicit-locking.html
[REF] select_or_create_state
and tests
[FIX] __openerp__.py PEP8
[FIX] TypeError: unlink() got multiple values for keyword argument 'context'
[IMP] using ir.config_parameter for geonames URL
[FIX] missing cr uid
Add support for states (if states are already present in res.country.state).
Add POT file and FR translation.
Allow to skip entries in the _prepare method.
Insist on the fact that the wizard deletes current better zip entries in the module description and in the wizard itself.
Better error message when the country code inside the file is wrong.
Add a FOR UPDATE NOWAIT at the beginning of the transaction.
Remove France-specific code ; moved to new module l10n_fr_base_location_geonames_import on lp:openerp-french-localization
Add module base_location_geonames_import
Add support for states (if states are already present in res.country.state).
Add POT file and FR translation.
Allow to skip entries in the _prepare method.
Insist on the fact that the wizard deletes current better zip entries in the module description and in the wizard itself.
Better error message when the country code inside the file is wrong.
Add a FOR UPDATE NOWAIT at the beginning of the transaction.
Remove France-specific code ; moved to new module l10n_fr_base_location_geonames_import on lp:openerp-french-localization
If merging 2 contacts, one with reference, and another without, and being the target
one the contact without reference, the constraint is raised as the reference value
is copied before unlinking the other contact.
We avoid it disabling the constraint when merging.
Before this commit, the partner_ref_unique could be changed on the
company even if existing partners share the same internal ref.
Therefore, errors will appear afterwards as DB already contains
duplicates although the policy shouldn't allow it.
With this change, the error will appear as soon as the policy is
changed, so that the data must be fixed before activating the
constraint.
OCA Transbot updated translations from Transifex
OCA Transbot updated translations from Transifex
OCA Transbot updated translations from Transifex
OCA Transbot updated translations from Transifex
OCA Transbot updated translations from Transifex
This contraint is self-disabled when it detects by context that it is being used from the contact deduplicator.
Otherwise, the user cannot deduplicate a contact selecting the "good" one as the one without reference.
Anyway, in these cases, the check has no meaning, since it is to avoid duplicates and in this context we are currently removing them.