Olivier Dony 9a5e317618 [FIX] OPW 592482: browse_record should not prefetch binary fields ... This was apparently a long-standing issue due to a strange handling of the _prefetch attribute on columns: accessing a column would only trigger the prefetching if its _prefetch attribute was True, but the prefetching itself would also prefetch columns that had _prefetch False. We clearly want it the other way around, or at least we want _prefetch to decide whether a column is included in any given prefetching pass. We can skip the prefetching pass when the only field being accessed has _prefetch False because it is likely the other fields have already been prefetched separately. This last subtlety should not make any noticeable performance difference. lp bug: https://launchpad.net/bugs/1177965 fixed bzr revid: odo@openerp.com-20130620131057-v7s4qfqj976j3ufo		2013-06-20 15:10:57 +02:00
..
__init__.py	API docs: settings file and titles at modules	2011-06-23 12:03:57 +03:00
expression.py	[IMP] clean permissions and shebang in files	2013-05-14 12:33:33 +02:00
fields.py	[FIX] OPW 592482: browse_record should not prefetch binary fields	2013-06-20 15:10:57 +02:00
orm.py	[FIX] OPW 592482: browse_record should not prefetch binary fields	2013-06-20 15:10:57 +02:00
osv.py	[FIX] *: fix/rationalize db logging to avoid incorrect values during logging	2013-03-01 13:07:44 +01:00
query.py	[REM] unnecessary parens	2012-12-14 13:38:03 +01:00