Community mailing list archives
Re: Migrate :: Persist from pre- to post-by
I was aware of property fields and xml_ids, the latter being imo rather simple to handle. The first, I haven't looked at it yet. As to translations would it not just be enough to ignore and update translations after update? Or do you think about custom defined translations, that could get lost?
Not quite true. It will only give you postgres foreign keys. Need to think about translations, properties, xml reference and possibly functional fields. Also sequences. Anygrate was a csv based migration tool I worked a lot on, solving this is not a simple sql statement.On Sun, 19 Jun 2016 2:52 PM David Arnold <firstname.lastname@example.org> wrote:This is the famous query to fish out all places relating to model. The first building block for the mentioned problem. For that it's worth sharing...HiI want to write an updating algorithm taking advantage of the new company dependent external ids created for accounts (1_account_2530).Basically what I want to accomplish is a check weather there was a change in the templates across module updating.Of course I would be able to simply create a temporary database table, BUT this would not automatically fetch present (and potentially future) many2many relationships as they are stored in separate (unkown at the time of coding) tables.Can you give me any advice on how to access/save pre-migration state across the data loding porcess?Thanks in advance!Best, David