Odoo is the world's easiest all-in-one management software. It includes hundreds of business apps:
CRM | e-Commerce | Accounting | Inventory | PoS | Project management | MRP | etc.
openerp-server help states that you can use the
-P option to import data from the command line.
-P IMPORT_PARTIAL, --import-partial=IMPORT_PARTIAL Use this for big data importation, if it crashes you will be able to continue at the current state. Provide a filename to store intermediate importation states.
From this I understand that I should run:
./openerp-server -P mydata.csv --stop-after-init
Is this correct? It doesn't seem to work.
And how do I "provide a filename to store intermediate importation states"?
Not quite. If you look at server/openerp/tools/yaml_import.py at line 330, you can see a bit more into what's happening. Also in server/openerp/tools/convert.py scattered between lines 817 and 935.
Normally when you import into OpenERP using the standard interface, it will process the entire batch at once, and then commit everything to the database if there are no exceptions raised during the import process. When you set --import-partial, you're committing after every single successful line to be imported. The file that you provide is the name of the file to dump the remaining records that were not imported once the failure occurred, so you won't have to import all of the initial, good records again until you solve every problem in the entire import.
tl;dr: It's not importing from the command line, it's altering how normal importing works.
About This Community
This platform is for beginners and experts willing to share their Odoo knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers.Register
Odoo Training Center
Access to our E-learning platform and experience all Odoo Apps through learning videos, exercises and Quizz.Test it now
|Asked: 5/15/13, 7:51 AM|
|Seen: 3610 times|
|Last updated: 11/6/15, 1:12 AM|