[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
