- RFQ wording imp
- products tree view in purchase form view: set account_analytic_id
for group_analytic_accounting only + add a context for the partner
- purchase: res_config: wording imp + config view imp
[IMP] Make autoreload work in --dev mode
- Replaced `pyinotify` by conditionally imported `watchdog`
- On code reload, restart process without losing --database argument (was crasing `odoo start` command)
- Removed `--auto-reload` in favor of `--dev`
[MERGE] Read ir.ui.view's arch from disk in development mode
A new switch named `--dev` has been added to the openerp.cli's arguments.
This development mode's purpose is to activate some specific behaviours in order to ease development.
For the moment, the only effect of `--dev` is to make the ir.ui.view's arch function field read the data from the original xml file (if any), allowing the developer to change a view and check the effect without having to update it's database.
This feature will currently work only with existing views. If you add a view you still have to update your database.
If any missing or partially incorrect values cause
an exception other than a psycopg2 error, we should
still catch it, rollback that record and report
the error, rather than letting bubble and fail
without any feedback to the user.
Fixes#1485
When we compute the discount of a product to display (result of product_id_change), we compare prices in the currency of the product while we expect prices in the currency of the pricelist. opw 606188
When a record is created, the magic fields (id, create_date,...) are first removed from the vals as the user should not set a value for these.
However if a value for this is given in default value (e.g. defined in an ir.value), the creation would crash (sql error : column specified more than once) as the magic column would be added again.
In some rare cases database records have negative IDs,
so the slug URL could look like /foo--20. This could
be mistaken for a slug ending with a `-` and a positive ID.
The latter is not supposed to happned as final hyphens
are stripped by slugify, but has been used in the past
and may be used in old links.
These parameters are (or should be) irrelevant for
a search_count(), and they could actually break the
result or make it significantly slower (e.g applying
`order` on large tables).
This fixes a performance regression introduced by
0f43032b.
We could also raise an error offset/limit are
passed in combination with count, but that seems
unnecessary.
Also switched to "SELECT count(1)" for the count
query, as it is simpler and just as fast.
We'd get the same perf with * or any constant value,
as in "SELECT count('me in')", but let's keep it
simple ;-)
tpa-odoo