@sraps,
After testing, It seems good, the idea behind is very good it allows to do a
lot of types of migrations from partail to complete ones in a controlled
manner. It is a kind of high level integrated ETL.
So congratulations you have done a nice Job
m2f -
@sraps,
> Probably have to look a bit closer, but I think it is not a good approach to
> place meta data inside the object itself.
>
> Concerns:
> 1) What would happen if we will try to migrate to next version? We will
> probably have to remove this meta data manually.
> 2) This process is
Try to look for field that has Field Type "Char" instead of "char" in 4.x
database...
Menu:
Administration->Custom->Low Level->Base->Database Structure->Fields
About migration from 4.2 to 5.0, yes, we have done that. Still, you have to
make analysis on all the enterprise processes, as this is al
Hi,
thanks for your response,
No filed has this upercase letter.The error refers to this line on ir_model.py
'ttype': fields.char('Field Type', size=64),
But i do not see any thing wrong in it !
On an other side did you manage to do a complete migration from 4 to 5 servers
using this approach ?
Hi,
thanks for your response,
No filed has this upercase letter.The error refers to this line on ir_model.py
'ttype': fields.char('Field Type', size=64),
But i do not see any thing wrong in it !
On an other side did you manage to do a complete migration from 4 to 5 servers
using this approach ?
> BTW,
>
> Also, just in case, for migrations, it's possible that the
> base_external_referentials (external ID's + custom mappings for each field in
> a declarative style), eventually combined with the etl module could help in
> your module...
> For now, the first on concrete application of b
[quote="rvalyi"]...@sraps,
Hey that's cool. We will try that for sure. Also, I did a relatively
sophisticated SQL/ORM API scripts to migrate my previous customers. Basically,
my script was trying to detect if there are records in ir_model_data that you
might have modified on purpose and that ar
@sam23
You have some incorrectly coded module which marks field with first upper case
character - "Char".
Anyway added this as exception.
Kaspars
---
http://kndati.lv
m2f
--
http://www.openobject.com/forum/viewtopic.php?p=45475#45475
Hi,
It is good idea to develop this module. I tested it and i get this error (if
load medata chexbox selected) :
OpenERP-Client Version : 5.0.6
Last revision No. & ID :Bazaar Package not Found !Traceback (most recent call
last):
File "/home/sam23/openerp506/server/bin/netsvc.py", line 244, in d
BTW,
Also, just in case, for migrations, it's possible that the
base_external_referentials (external ID's + custom mappings for each field in a
declarative style), eventually combined with the etl module could help in your
module...
For now, the first on concrete application of base_external_re
@sraps,
Hey that's cool. We will try that for sure. Also, I did a relatively
sophisticated SQL/ORM API scripts to migrate my previous customers. Basically,
my script were trying to detect if there are records in ir_model_data that you
might have modified on purpose and that are likely to be ove
Hello!
We are pleased to announce the release of data migration module for OpenERP.
This tool will help automating data migration process from one database to
another. It will help moving data between databases not only 4.2. to 5.0., but
also between two 5.0. installations.
Information about
12 matches
Mail list logo
