[res_country] : Create country  without code or remove country code raise error
[FIX] re-importing the translation from a file(.csv, .xml) updates the terms in ir_translation table but does not update it in cache memory, need a server restart to take those change effect in interface. (Maintenance Case: 587178)
[IMP] use ORM reads when loading views

direct SQL query in core ORM means we can't override view loading to
get them from other sources than the database. By using read() this
can be done by overriding ir_ui_view.read.
[IMP] move raw SQL to ORM

Improves maintainability, required adding a fake-ish o2m field to
ir.model.data to handle join.
[IMP] move locate inner function to ir.ui.view method
[IMP] add tests for locate_node
[IMP] Element.getiterator -> Element.iter

> Note that this method is deprecated as of ElementTree 1.3 and lxml
> 2.0. It returns an iterator in lxml, which diverges from the
> original ElementTree behaviour. If you want an efficient iterator,
> use the element.iter() method instead. You should only use this
> method in new code if you require backwards compatibility with older
> versions of lxml or ElementTree.
Temporarily disable XML validity check (calls fields_view_get, PITA)
[ADD] some tests for get_inheriting_view_arch

Tests are way incomplete: no test for partial loading or groups filtering
[ADD] depth-first iterator on views, refactor apply_view_inheritance to use it
[FIX] temporarily remove _init flag of pooler during view inheritance test

Breaks between in-loading (openerp) and unit test (oe), behavior is
crap and can't be arsed to create a dummy ir.model.data for that.
[IMP] attempt to remove lexical dependencies from fvg's nested functions

should allow moving most of the view inheritance application into
ir.ui.view, where it should belong.
[FIX] don't 'double tap' when applying view inheritance

iter(exclude_base=False) would add the base view (being extended) to the sequence, and thus start by extending the base view with itself.
[REF] move apply_inheritance_specs to ir.ui.view

also moved raise_view_error utility function
[IMP] move resolution of view_ref outside of root-ancestor-searching loop
[IMP] move fetching of root view into ir.ui.view
[ADD] tests to get_root_ancestor

use a default view_type of form in the tests, because whatever
[ADD] tests for *not* finding root views
[IMP] move view_id initialization out of loop, make flow simpler
[IMP] simplify ir.ui.view.get_root_ancestor by using browse records

Also only case which should result in the id not existing is the
initial record, if a view_id is explicitly provided. So the loop can
avoid it's, it's traversing through an m2o so if the m2o value is not
null the next record in the chain should always exist.