* Performance was very poor due to several reasons:
* City name translatable.
* Lack on indexes when deleting obsolete records.
* Some prefetching.
* City was not being searched also by state, having the chance of returning
incorrect matches if same city name on different states.
* Previous code was removing all previous records of zip entries!
* Remove possible obsolete FK keys after migrating from v11.
If there are several cities with the same name in different states, previous code doesn't
handle correctly this situation.
We amend this storing in the cached dictionary both city name and state.
Includes a test for checking this specific condition, got from real data in US.
Fixes#749
* [IMP] base_location: Add lat & long to `better.zip`
* Add latitude and longitude columns to `better.zip`
* [IMP] base_location_geonames_import: Add lat/long
* Add support for latitude & longitude to genomes importer
* Tests
* New menu location
* Wizard options fixed
[IMP] base_location_geonames_import
* Speed improvement applying cache for not doing duplicated searches
over states.
* Tests change to SavepointCase, which only passes over setUp one time.
[IMP] base_location_geonames_import: Make tests more efficient
[FIX] base_location_geonames_import: Don't alias Warning
[IMP] base_location_geonames_import: Convert tests to Python + switch imported country
Monaco country is very little and it allows to save some downloaded bytes plus making
a test for entries deletion
[IMP] base_location_geonames_import: Switch author
[FIX] base_location_geonames_import: Fix test
[FIX] base_location_geonames_import: Fix tests
[MIG] Make modules uninstallable
[MIG] Rename manifest files
[FIX] base_location_geonames_import: Test logic changed
For avoiding constant problems with this test, as Monaco data changes a lot,
what we are testing now is the existence of the data, not the exact match of them.
* Added Icon.
* Improve module description and extracted to README.rst.
* Pass country instead of country_id for advance comparisons.
* Allow to transform city name.
* Some code style.
* Do not remove all entries of a country, but only not found.
* Include hooks for transforming some things.
* Include spanish translation.
[FIX] base_location_geonames_import: Use self.env and recordsets
[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.