[FIX] Correct remaining SQL now() calls, must use UTC
authorOlivier Dony <odo@openerp.com>
Mon, 20 Feb 2012 10:59:43 +0000 (11:59 +0100)
committerOlivier Dony <odo@openerp.com>
Mon, 20 Feb 2012 10:59:43 +0000 (11:59 +0100)
commit3f6524a6e2b379e1ed9858510ab17a2fcfc78c05
treef393457a9fa7bd1a17d0809553ed3b9278db3d7c
parentf95d98807c39794ed82f22038c72c7c64a1bf19b
[FIX] Correct remaining SQL now() calls, must use UTC

This is essential to have the proper behavior for
timestamps: on the database side we exclusively
store UTC data (no DST issues, etc.) as naive
timestamps (to prevent Postgres from messing with them).
Inside OpenERP server/addons we work again with
pure UTC data (much simpler), and only render
them according to the user's timezone when they
are displayed in the user interface or rendered
in a PDF report.

lp bug: https://launchpad.net/bugs/918257 fixed

bzr revid: odo@openerp.com-20120220105943-v3m0i50phrurt8x6
openerp/modules/loading.py
openerp/osv/orm.py