openerp-expert-framework team mailing list archive

[Thibaut DIRLIK <thibaut.dirlik@xxxxxxxxx>]

Hi,

Imo the solution would be the pass a browse_record_list instead of a ids to
every functions. Because of the lazy loading of browse_records, they won't
be loaded (= no query) if the browse is not used. And for every other
cases, the browse's cache will be used between functions call (super(),
etc).

And you still can use browse.refresh() to clear the cache if you need.
That's typically a use case for _constraints : every contrains does its
browse. Why not just pass the same browse_record_list to every constraints
methods ? I don't understand.

2012/8/15 P. Christeas <xrg@xxxxxxxx>

> On Wednesday 15 August 2012, Leonardo Santagada wrote:
> > 2012/8/15 Raphael Valyi <rvalyi@xxxxxxxxx>
> > > On Wed, Aug 15, 2012 at 12:54 AM, Raphael Alla <
> raphael.alla@xxxxxxxxxxx>
> wrote:
> > I get that they developed their own because there wasn't any good orm
> > 10 years ago. Today I think the SQLAlchemy branch is fastest path to a
> > sane DB usage. No need to do query rewriting, just make OpenERP
> > postgresql only but using SQLAlchemy...
>
> Do you have any experiments, any numbers?
>
> Any code to back these wishes?
>
> Typical times to build a new OpenERP db, with all standard modules:
>
> 6.0 :    450 sec
> 6.1:     500 + * (with many modules being broken and excluded)
> pg84:  280 sec
> F3:      250-270sec
>
> Sadly, the 6.0/6.1 have intentionally refused to accept dimensioning
> patches
> (the ones that allow query stats or repetitive procedures; eg. Nx sale
> orders). So we cannot compare the other operations.
>
> --
> Say NO to spam and viruses. Stop using Microsoft Windows!
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-framework
> Post to     : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-framework
> More help   : https://help.launchpad.net/ListHelp
>