| Age | Commit message (Collapse) | Author |
|
|
|
To avoid scenario as in 11346 where the report expects a currency symbol.
|
|
Make the field reflect the field property `store` in registry.
|
|
NB : Some tests have been modified.
One assert statement in orderpoint_calendar.yml has been modified,
but the change is legit has no python method has been modified at all
|
|
field `indexed`
|
|
Also add a constraint on the value of field `related`, and corresponding
onchange methods.
|
|
The fields are properly reflected for base many2many fields. Moreover, the
code has been improved to remove a custom many2many field whose table is still
used by another field.
Onchange methods have been added:
- When name, model and comodel are chosen, propose table and column names.
- When table is modified, propose column names if the table is already used by
another many2many field.
|
|
* add missing columns in base.sql
* add missing fields 'help', 'readonly', 'required', 'selectable' in reflection
* add field 'help' in `ir.model.fields` views
* do not patch registry with translated field string and help upon `ir.model.fields` update
|
|
Rename the field 'osv_memory' on 'ir.model' into 'transient', and make it a
regular field instead of a computed one. When instantiating a custom model,
use its value to make transient models.
This commit alone will make your server crash on an existing database. A small
database migration is needed: simply add a boolean column `transient` (with
default value false) in table `ir_model`.
|
|
When a module is updated, the sql constraints were checked against postgres pg_get_constraintdef() to see if they have diverged from the one defined in python code.
However this check was failing as the syntax returned by pg_get_constraintdef() (e.g. "CHECK ((credit * debit) = 0::numeric)") differs from the one returned by `unify_cons_text` method (e.g. "check(debit*credit = 0")) so the constraints were always dropped and recomputed.
This adds a definition column on ir.model.constraint (storing original defintion) to detect changes.
The pg_constraint is still inspected to make sure we detect constraint without ir_model_constraint but with postgres constraint defined (e.g. name_uniq defined in base.sql).
This changes also the date_update field when the definition changes.
|
|
|
|
[FIX] force creation of workflow used columns.
bzr revid: chs@openerp.com-20140425162828-e85aut02ua8c53nv
|
|
bzr revid: chm@openerp.com-20131202150856-fzrfcoa8pmsjutau
|
|
Size limits prevented some database models customization (like selection fields with selection options longer than 128 chars)
bzr revid: dle@openerp.com-20131108130208-srt5gzlxbk890htf
|
|
bzr revid: al@openerp.com-20130625162755-d6552p98m5jiw941
|
|
first argument in property fields definition
bzr revid: qdp-launchpad@openerp.com-20130619091332-29pisdnyfemn1u3d
|
|
* Formally make model not required
* Remove idiotic default values on type and arch
* Make type not required (it's a function field!)
bzr revid: xmo@openerp.com-20130426145113-cf0t0xx24lk9mtgs
|
|
models `auto_init`ed multiple times
The case where no constraint existed at all was not working,
and after fixing it, the ORM started to re-create the same
constraints multiple times for some modules. This was for
models that are split within a module (such as res.users in
base, which is made of several small classes): all the
partial models were going through _auto_init instead
of only the final one - doing useless extra work.
Unfortunately establishing the FK happens before the
XML data files are loaded, so a number of FK and
NOT NULL constraints failed to apply due to missing
tables/records. base.sql had to be extended a bit
to cover these cases in a minimalist fashion
bzr revid: odo@openerp.com-20121217214645-av9n003yzterhujw
|
|
bzr revid: fme@openerp.com-20121122152159-a9lxb4fwn8qkvsvt
|
|
bzr revid: fme@openerp.com-20121122151425-fr8o1v587vgmnf5f
|
|
bzr revid: fp@tinyerp.com-20120926121536-9836j42ulu8wcir8
|
|
bzr revid: tde@openerp.com-20120813093656-ywab7wjdpc5gwl02
|
|
ORM being unable to set a not null constraint on it.
bzr revid: tde@openerp.com-20120810140549-w70l7nzwn4kt1oav
|
|
not context_lang anymore; tz, not context_tz.
bzr revid: tde@openerp.com-20120810081836-y4f2nsft9g7p4hl6
|
|
bzr revid: jam@tinyerp.com-20120717085028-2jkbf9ymrftkui45
|
|
bzr revid: vmt@openerp.com-20120620100705-p9o5kktmj8zkbshm
|
|
of overlaoding ir.model.data.
bzr revid: vmt@openerp.com-20120601153449-uj2sl7qjzz3s7xnj
|
|
bzr revid: vmt@openerp.com-20120531160140-tutjw76tp0u5hipo
|
|
bzr revid: xmo@openerp.com-20120420152220-1yo0rykkj45jfee0
|
|
bzr revid: vmt@openerp.com-20120130095238-x2by4y11joeytipr
|
|
`auto_installable`. An auto-installable module is a module automatically
installed by the OpenERP server as soon as its dependencies are
satisfied, without explicit user action.
bzr revid: vmt@openerp.com-20120126164049-smrcvrojy0b1z6f8
|
|
individual module manifests
Having the sequence number living outside the module itself
causes various problems at initialization when modules are
missing (e.g. if creating a database with `base` only).
It is also cleaner to have the module sequence in the
module manifest, like other module metadata.
A corresponding commit in the addons project adds the
`sequence` field in the manifest of all modules who
have a non-default sequence (the main apps).
bzr revid: odo@openerp.com-20120107041745-tik3iu1b2qs4ym85
|
|
6 times faster)
bzr revid: rco@openerp.com-20111223104824-fup1cjbjni1fsty1
|
|
bzr revid: odo@openerp.com-20111222102555-bydsozbdu6urkj31
|
|
bzr revid: al@openerp.com-20111208222241-n9raoe1jec4llh26
|
|
bzr revid: chs@openerp.com-20111208145101-oth2k8xuymze7y2l
|
|
bzr revid: fp@tinyerp.com-20111206111531-qdkajwatqzb0dz45
|
|
bzr revid: vmt@openerp.com-20111201153214-0iintvpp7crnr2jc
|
|
bzr revid: odo@openerp.com-20111116172525-rmri79n9hpf2plwg
|
|
bzr revid: stw@openerp.com-20110930095814-4o01upd0krmysbid
|
|
change request in base.sql as a new field is created in ir_model_fields
bzr revid: sebastien.beau@akretion.com.br-20110920170707-2wmfs1sg37hgvbl1
|
|
bzr revid: xmo@openerp.com-20110630115134-m5tppqs9whmqtqow
|
|
select fields validate themselves in ORM, through _check_selection_field_value(),
which /retrieves/ the .selection list and checks if value to be written
is among possible ones. This, however, is very expensive for models that
have variable selection lists (eg. ones that require an SQL query).
In fact, for ir.translation, the query would be repeat for every single
write() to ir.translation. The 'lang' field is actually a reference for
res.lang.code (not the .id, sadly), so let SQL implement the constraint
for us.
bzr revid: xrg@linux.gr-20110608093254-ua66p5co6dc203zs
|
|
- added the "translate" column to ir_model_fields in base.sql
- modified orm.py to correctly set that column
- this is based on a patch by xrg.
lp bug: https://launchpad.net/bugs/780584 fixed
bzr revid: vmt@openerp.com-20110523132153-njovr5ynt66k8d81
|
|
- Some logging code moved from netsvc.py to loglevels.py
- Changed imports to use the new openerp module
- config and netsvc initialization calls move to openerp-server.py
- Moved openerp-server.py outside the old bin directory
- Some imports in tools moved inside the methods to break mutual-dependencies
bzr revid: vmt@openerp.com-20110207125723-ooee7d7ng5elmkso
|