Hi Piotr Bienkowski 

Unknown said:

Do translation memories used in Studio 2017 need any upgrading to ver. 2019?

No

Unknown said:

Can I open the 2017 project templates directly in 2019 or will it break them? (I understand that I can use the migration utility to migrate them).

You can't use the project migration utility to migrate templates.  It's always a good idea to recreate your templates because otherwise you potentially introduce legacy problems into the newer product.  There are also new features between versions and if you use the old template you create projects without access to the latest stuff.

Unknown said:

Can I open projects created in Studio 2017 in Studio 2019 or will it break them? WIll they be backward-compatible if I open and save them in Studio 2019?

Yes you can. But as you can use Studio 2017 for as long as you like this time around it makes sense to finish them off in 2017 and start new ones in 2019.

Unknown said:

The translation memory data file engine returned an error:

constraint failed

UNIQUE constraint failed: translation_unit_contexts.translation_unit_id, translation_unit_contexts.left_source_context, translation_unit_contexts.left_target_context

Hi Michael

I have the same issue with several of my TMs, also in Studio 2019.

Did you find a solution to this problem? (I don’t have a contract either)

Alexa