openerp-community team mailing list archive

[Ferdinand <office@xxxxxxxxxx>]

A performance issue should be observed if o2m relations are to be inserted
avoid to create the "m lines" one by one but pack them into the 
create/write statement of the "o line"
have a look in v7 stock/stock.py lines 2356-2360
it is really important to avoid recalculation of "o line" computations


On 2013-08-06 17:18, Brendan Clune wrote:

> Dale,
>
> What Nhomar means is that it is almost always better to interact with 
> OpenERP objects than it is to operate at the database level. When an 
> object is created through OpenERP's ORM (object relational mapping), 
> OpenERP applies some business logic and additional constraints that 
> don't occur at the database level. Without using this business logic, 
> it can be easy to enter data that is not in a consistent state---in 
> OpenERP this manifests itself as frequent and rather cryptic errors.
>
> Using a scripting language to enter data into OpenERP will let you use 
> the ORM to ensure that your data is consistent. This is the XML-RPC 
> interface that Nhomar mentioned, and is almost certainly the preferred 
> method.
>
> You can see examples of what such a script might look like here:
> https://doc.openerp.com/6.0/developer/6_22_XML-RPC_web_services/
>
> Hope this helps,
> Brendan
>
>
> On Tue, Aug 6, 2013 at 12:28 AM, Dale Scott <dale@xxxxxxxxxxxxx 
> <mailto:dale@xxxxxxxxxxxxx>> wrote:
>
>     Thanks for your comments Nhomar and Martin. It's good to hear this
>     approach
>     is feasible.
>
>     Martin,
>     > Then you can figure out what shape it needs to be for OpenERP
>     and you will
>     be
>     > well placed to import it, perhaps with the aid of a custom
>     OpenERP module.
>
>     By custom, do you mean a custom third party module?  Are there any
>     you would
>     recommend? Or do you mean a custom module I write? I watched
>     "OpenERP 7 -
>     Import data using XML-RPC and Python Script " from OpenERP Consulting
>     (http://www.youtube.com/watch?v=goh6swXRYns&list=PLdwc-_Ljcrkovnrn_aE7bbbrmP
>     acloADt&index=1
>     <http://www.youtube.com/watch?v=goh6swXRYns&list=PLdwc-_Ljcrkovnrn_aE7bbbrmP%0AacloADt&index=1>).
>     Is this procedure the typical method?
>
>     Nhomar,
>     > 2.- Process Quality, if you instead of use only csv use xml-rpc
>     mixed with
>     csv you
>     > will be able to emulate people reading the legacy and putting
>     data in the
>     new one,
>     > with this, you will observe process decistions that in the initial
>     meetings is almost
>     > impossible to kow that you need.
>
>     can you please explain this workflow in more detail? I'm not
>     understanding
>     the significance of this approach.
>
>     Thanks everyone,
>     Dale
>
>     BTW, I'm using MySQL for legacy data only due to familiarity. I'd
>     like to
>     use PostgreSQL eventually, but at least it's consolidated in one
>     place for
>     now.
>
>
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~openerp-community
>     <https://launchpad.net/%7Eopenerp-community>
>     Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>     <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~openerp-community
>     <https://launchpad.net/%7Eopenerp-community>
>     More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> --
> Brendan Clune
> Information Technology
> Logic Supply, Inc.
> Direct: 802 861 7459 | Main: 802 861 2300
> www.logicsupply.com <http://www.logicsupply.com> | www.lgxsystems.com 
> <http://www.lgxsystems.com>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp


--
Ferdinand