On Monday 14 February 2011, you wrote: > The default values have been changed to count=False (disabled, it used > to be 200) and age=1.0 hour, so that with the default config the server > will only expire osv_memory records...
Yes, but may I remind, Olivier, this simple design fact about osv_memory records: *** osv_memory records are VOLATILE, they are designed to be only temporary storage of data for the purposes of intermediate steps, like the wizards *** we must keep that in mind[2] and never expect them to reliably _store_ data. And this design fact does invalidate the proposals to have "orm_memory pointed to by plain orm records", or just have high limits etc. My personal opinion is this: if we need to store some small amount[1] of wizard decisions, yes, orm_memory storage is appropriate. If we need to edit thousands of lines (which a human would take some hours to review), then we should reconsider and use some regular ORM model instead. If, like in the stock.partial.picking, we only use the list to display the set of records we are about to process (but don't expect the user to edit them all one-by-one), an orm_record may marginally be valid, though. [1] a "small amount" can be subjective. In some cases 1-10 records, sometimes even 1000. [2] please don't hammer us describing that as a bug. It was designed to work that way and you have to understand that. _______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
