* In cases of deep inheritance, it may be required to create an adapter directly. Add an override in the create via the env context to support this.
* Add default system type if creating from an interface
* Fix interface assignment during creation in adapter
* [ADD] base_external_system: Implement interface/adapter for external systems
* base_external_system: Fix OS model, add inherits, add validate
* base_external_system: Usability and private key pass
* base_external_system: Use contextmanager in adapter client
* base_external_system: Move contextmanager to interface
* base_external_system: Include contextmanager on adapter and system
* base_external_system: Unify client
* Use password widget for password field
* Add tests & security
* Fix lint
* Add plaintext note
On 9af8b31d921dcccb7bcf230271fd3ef4R4329, a new keyword argument was added
for `_browse`, so any overriding needs to add that argument, as it's the case
for this module.
Includes:
- Normal migration steps.
- Usage of brand new `_inherit = "base"` in Odoo 10, which implies
removing a lot of monkey-patching code.
- Log a warning when multiple matches are found.
* Fix wrong README format.
* [FIX][base_import_match] Avoid UnicodeEncodeError.
When the model or field you chose was translated and had some non-ascii
character, you got an error like this: `UnicodeEncodeError: 'ascii' codec can't
encode character u'\xed' in position 15: ordinal not in range(128)`.
Now, using unicode strings, that won't happen again.
* Do not require a hidden field.
* Further unicode protection, add ondelete clause.
By default, when importing data (like CSV import) with the ``base_import``
module, Odoo follows this rule:
1. If you import the XMLID of a record, make an **update**.
2. If you do not, **create** a new record.
This module allows you to set additional rules to match if a given import is an
update or a new record.
This is useful when you need to sync heterogeneous databases, and the field you
use to match records in those databases with Odoo's is not the XMLID but the
name, VAT, email, etc.
After installing this module, the import logic will be changed to:
1. If you import the XMLID of a record, make an **update**.
2. If you do not:
1. If there are import match rules for the model you are importing:
1. Discard the rules that require fields you are not importing.
2. Traverse the remaining rules one by one in order to find a match in
the database.
1. If one match is found:
1. Stop traversing the rest of valid rules.
2. **Update** that record.
2. If zero or multiple matches are found:
1. Continue with the next rule.
3. If all rules are exhausted and no single match is found:
1. **Create** a new record.
2. If there are no match rules for your model:
1. **Create** a new record.
