Re: [Tinyerp-users] Server Data Migration module released

2009-10-20 Thread forum-user
@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 

--
http://www.openobject.com/forum/viewtopic.php?p=45566#45566

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-20 Thread forum-user
@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 being done once (maybe several times, doing it partially), 
> and there is no need to place mappings side bu side with the data itself. 
> This approach is better for systems that should be kept synchronized 
> constantly, so the process is being done again and again. 
> 
> But still it is superficial opinion, and it would be nice to hear your 
> comments on this...


Actually we now using the ir_model_data for bookeepng external ids. This has 
been debated long with Fabien Pinckaers and Sharoon Thomas over #openobject IRC 
those last days. This isn't going to impact visible perf due to the fact that 
external synch as other bottlenecks such as webservices.

Object mappings metadata is not inside the business objects either.

We will let you know soon about our migration script.


Raphaël Valyi

CEO and OpenERP consultant at
http://www.akretion.com




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45539#45539

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-20 Thread forum-user
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 almost the same as 
implementing new ERP. TinyERP slightly differs from OpenERP.

The tool is to automate reentering the data and do some analysis on data 
structures.

With the tool we can do migration for the customer a lot cheaper. There are 
cases when reentering the data is not an option at all, so this is the only 
option to do a migration.

We can provide partial or full migration services for customers.
This can be as simple as ready made model mappings, or complete process 
analysis and modification services.


Kaspars

http://kndati.lv




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45523#45523

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-20 Thread forum-user
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 ?




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45513#45513

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-20 Thread forum-user
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 ?




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45512#45512

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-20 Thread forum-user

> 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_referentials is 
> the new multi instance refactored Magento connector we are shaping here:
> https://code.launchpad.net/magentoerpconnect


We do all the mapping for objects in "memory", this is probably better for 
performance but maybe not so good in terms of handling huge data.


> This module provide an abstract common minimal base to add any additional 
> external id columns to some OpenObject table, pointing to some external 
> referential.
> A referential is abstract and minimal at this stage, it's only identified
> by:
> * a name
> * a location (possibly webservice URL, database connection URL...); the 
> connection method will tell it...
> * referential credentials (user name + password)


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 being done once (maybe several times, doing it partially), 
and there is no need to place mappings side bu side with the data itself. This 
approach is better for systems that should be kept synchronized constantly, so 
the process is being done again and again.

But still it is superficial opinion, and it would be nice to hear your comments 
on this...

Kaspars
--
http://kndati.lv




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45488#45488

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-20 Thread forum-user
[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 are likely to be overriden after 
upgrade using --update=all. So it warns you for each records so you can take a 
decision manually record per record.

Let us know what you think about the idea and if we should team more closely to 
make sure we have the smoothest migrations.
[/quote]

Would like to look at your script. It is definitely better to add more 
inteligence to the module, to make it more useful "out of the box".

The next step would be to perform meta data analysis on the fly, some sort of 
checks to find possible "tar pits".

This could be addressed in two ways:
1) try and error;
2) extensive analysis.

[quote="rvalyi"]
On other remark: instead of using a blog for tracking API changes, I suggest 
Tiny could simply tag the branches at each API changes so it would be more all 
in one single place and a filter on tags will help tracking all the API changes 
between versions X and Y.

Regards and thanks for the module.[/quote]

Absolutely agree with you.

Additionally some other way of API documentation should be introduced. For Perl 
language the documentation placed inside code, and displayed/filtered out by a 
tool. Actually all the API documentation on the modules and core is being 
organized this way. So it is easier to update API doc when the changes are 
being done.

As I am not exactly skilled Python programmer, do not know of similar thing for 
it.

Kaspars
--
http://kndati.lv




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45483#45483

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-20 Thread forum-user
@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

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-19 Thread forum-user
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 dispatch
result = LocalService(service_name)(method, *params)
  File "/home/sam23/openerp506/server/bin/netsvc.py", line 73, in __call__
return getattr(self, method)(*params)
  File "/home/sam23/openerp506/server/bin/service/web_services.py", line 639, 
in execute
return self._execute(db, uid, wiz_id, datas, action, context)
  File "/home/sam23/openerp506/server/bin/service/web_services.py", line 619, 
in _execute
return wiz.execute(db, uid, self.wiz_datas[wiz_id], action, context)
  File "/home/sam23/openerp506/server/bin/wizard/__init__.py", line 178, in 
execute
res = self.execute_cr(cr, uid, data, state, context)
  File "/home/sam23/openerp506/server/bin/wizard/__init__.py", line 169, in 
execute_cr
return self.execute_cr(cr, uid, data, next_state, context)
  File "/home/sam23/openerp506/server/bin/wizard/__init__.py", line 168, in 
execute_cr
next_state = result_def['next_state'](self, cr, uid, data, context)
  File 
"/home/sam23/openerp506/server/bin/addons/server_migration/wizard/configuration.py",
 line 101, in _save_data
field_obj_id = field_obj.create(cr, uid, f)
  File "/home/sam23/openerp506/server/bin/osv/orm.py", line 2641, in create
% (vals[field], field))
except_orm: ('ValidateError', 'The value "Char" for the field "ttype" is not in 
the selection')




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45463#45463

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-19 Thread forum-user
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_referentials is the 
new multi instance refactored Magento connector we are shaping here:
https://code.launchpad.net/magentoerpconnect


Raphaël Valyi

CEO and OpenERP consultant at
http://www.akretion.com




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45456#45456

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


Re: [Tinyerp-users] Server Data Migration module released

2009-10-19 Thread forum-user
@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 overriden after 
upgrade using --update=all. So it warns you for each records so you can take a 
decision manually record per record.

I've seen that CampToCamp also had concerns about security settings being 
overridden with --update=all. In my option our script is the answer to all that.

We've got a trainee now at Akretion.com so hopefully he will help sorting this 
out. I'm not sure whether our script would be better integrated in your module 
or the base_module_recorder module.

Let us know what you think about the idea and if we should team more closely to 
make sure we have the smoothest migrations.

On other remark: instead of using a blog for tracking API changes, I suggest 
Tiny could simply tag the branches at each API changes so it would be more all 
in one single place and a filter on tags will help tracking all the API changes 
between versions X and Y.


Regards and thanks for the module.


Raphaël Valyi

CEO and OpenERP consultant at
http://www.akretion.com




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45455#45455

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users


[Tinyerp-users] Server Data Migration module released

2009-10-19 Thread forum-user
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 this module you can read on our web page.
http://kndati.lv/index.php/en/openerp/open-erp-addons/data-migration

Module source code is available on Launchpad project:
https://launchpad.net/datamig

Latest release in zip'ed format is available also from our web page:
http://kndati.lv/index.php/web-links/44-open-erp-addons

There is also forum for community communication and bug reporting on our web 
page:
http://kndati.lv/forum/

Please note that this is tool to help you automate the migration process, not 
to do the process for you.


Best regards,
Kaspars
-
http://kndati.lv




 m2f 

--
http://www.openobject.com/forum/viewtopic.php?p=45431#45431

 m2f 


___
Tinyerp-users mailing list
http://tiny.be/mailman2/listinfo/tinyerp-users