when test is run right at the boundary between two seconds, after rounding to second generated date and reference date could differ.
check that generated date is within a small range (date created before and date created after) instead of equal to reference
bzr revid: xmo@openerp.com-20121210165006-y720xrwlo37sjwm8
expression.parse: refactored the main parsing loop, now using source and result stacks. Leaf elements are encapsulated into a specific object, allowing to delegate the join condition formation, working table management and table aliases generation to them. The parsing is now a simple loop taking a leaf, doing one action on it, and putting the result back to be analyzed or in the results. This allows to avoid having nested loops and uncontrolled results.
Other modifications :
- updated the generation of order_by to take into account the table now referred using aliases
- updated Query object to use the aliases
- fixed an outstanding bug about _order, now handled as order. This means that putting direct SQL into _order of models will not be supported anymore, because of the computing complexity now that we have multiple joins in queries. The branch holds the patch from Paulius Sladkevičius
- updated and added tests
- added a basic documentation for the freature
lp bug: https://launchpad.net/bugs/1070757 fixed
bzr revid: tde@openerp.com-20121210154652-6sab9usb38i7adlh
mail_thread
- updated the message_unread function field, now returning a domain on mail_message notifications. This domain is quite complex and redundant, but mandatory in 7.0 considering the limitations of _auto_join
- message_ids is now using auto_join
- removed message_comment_ids field, not necessary and that lead to confusing data on kanban views
mail_message:
- notifications_ids is now using auto_join
- refactored the todo, now delegated to the notifications
- the favorite_user_ids field is therefore removed, and various methods updated
- updated _search_to_read and _search_starred to return a domain on notifications
- updated the domains of the mailboxes accordingly
bzr revid: tde@openerp.com-20121210154452-ngy6lw1jg97ib5gn
Editable list was losing value when switching to other row from edited
cell (edit, tab-to-next-fiend then change record worked).
When changing row (by clicking on an other row or pressing up/down),
the list view simply request saving the current form and — once that
is done — switches the form to the new row.
The issue is in what happens *during* form-saving: for most text-based
fields (e.g. CharField-like) the field returns its internal
value. Said internal value was only synchronized when the internal
form control (input or textarea) fired the ``change`` event... and the
change event only fires *after blurring* (leaving) the current
field. So the form saving (and thus the retrieval of field values)
occured before the field could sync its internal value with the one
entered by the user.
Added a bunch of commit_value override to perform this synchronization
right before the field's value is requested.
Also removed an extraneous trailing comma in an array, and removed 2
useless temp storage (unused variables beyond their assignment).
bzr revid: xmo@openerp.com-20121210143808-wt4jmi4x0pg85xb8
I believe there are potential circular imports that can break
because of openerp.modules.module ImportHook, but they are
deifficult to reproduce when the import order is not always
the same.
bzr revid: vmt@openerp.com-20121210140411-ranw3jc3mwu3ymty
Server-side branch:
- needaction_enabled field on ir_ui_menu is now stored
- needaction_counter field on ir_ui_menu removed
- counters are accessible through get_needaction_data, called by the web client independently of the menu entries
bzr revid: tde@openerp.com-20121210131753-gtw4nyo5kosroq00
This web revision modifies the way needaction are loaded. Now they are loaded independently of the menus. After having loaded and displayed the various menus, a call to the server is done to avoid a long latency between the login and the display of menus. Needaction counter will be displayed as soon as they are available.
bzr revid: tde@openerp.com-20121210131658-pgy3t9t71f0z2yd5
these events are used by the autocompletion widget internally, if they
bubble upwards they also get handled by the list view which interprets
them as going up/down the list.
Prevent the latter by suppressing bubbling of these events.
bzr revid: xmo@openerp.com-20121210112203-3mry0pvecri0pv9o
Otherwise, if a search is performed while creating or editing a line
(e.g. in logged calls, create a line without saving then try to apply
a filter) the edition section (and new line) disappears but the list
remains in "edition" mode (e.g. save/discard button) even though
edition data is missing (trying to save or discard will error out).
bzr revid: xmo@openerp.com-20121210100914-delia5bhmtgrujpu
Launchpad Translations on behalf of openerp
Antony Lesuisse
Fabien Pinckaers
Xavier Morel
niv-openerp
Thibault Delavallée
Raphael Collet
Fabien Meghazi
Vo Minh Thu
Christophe Simonis