summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMartin Trigaux <mat@odoo.com>2017-02-16 14:31:24 +0100
committerMartin Trigaux <mat@odoo.com>2017-02-16 15:34:52 +0100
commita2cf865dfe7b83ba610780da4b078c026c5e262e (patch)
tree9f6748b78fad4468a719b05d32be1a83fd446915 /doc
parent5ed80452d1411da83ec74bc9464329964a5d2531 (diff)
[FIX] point_of_sale: use valid sequence on pos.order.line
2 sequences are created when a pos.config is created: - one for pos.order, stored in sequence_id field - one for pos.order.line, link is lost, like dust in the wind ♫ When creating a pos.order.line from a new order, the default value was using the first sequence if found using the code 'pos.order.line' (returning the latest created). The name of the line was always using the same sequence, whatever the config used. In master, the field has been stored at 645df676 but in stable version, the following hack is done: As the sequences are created in the same transaction as the pos.config, the create_date will be the same to the microsecond. The name of the config can not be used as too easily changed (e.g. duplicate) and may not be unique. Done in SQL to avoid ORM cleaning of microseconds, not working with a search. opw-703092
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions