Important: This page is using cookies (cookies). Using this website without turning off cookies in browser, means that you agree for using it.
Buy Now! Features Downloads Check vBET on vBulletin 5

Earn with us!

If you would like to start earning money with vBET join to Affiliate Program.
Results 1 to 3 of 3

Thread: Сonsolidate translation databases?

  1. #1
    Member
    Join Date
    Aug 2010
    Posts
    73

    Default Сonsolidate translation databases?

    Hello!
    Version 4.9.2
    There is an old (2012-2016) external database of 5 GB and a new (2017-2018) external database of 2 GB. Can I unite them?
    Сombine translation databases so that the translation of messages 2012-2016 were from the old database, and messages 2017-2018 were from a new database?

    Thank you!

  2. #2
    Michał Podbielski (vBET Staff) vBET's Avatar
    Join Date
    Oct 2009
    Posts
    2,988
    Blog Entries
    1

    Default

    Hello,

    First of all it will be very wise to combine those databases, because now you don't have access to all of your translations, so those are taken again from providers, what lower performance and in case if you are using paid providers also creates additional costs (you can use vBET with only free translations).

    Simplest approach is to dump to SQL file cache tables from new database and then execute the SQL on old database. Just make sure that the SQL doesn't include drop table instructions (nor create). This is simplest because, as I assume, you will move less data, but this way for doubled translations you will stay with older version (because of unique constraint on original text).
    If you move old one to new one, then you will move more data (assuming by time period), but for doubled translations you will stay with new ones.
    Also please note that because of limitations of MySQL, for very long tests to translate there is no unique constraint, so those can be doubled in your database. It will not harm your application, you will just loose some HDD space.

    Also - first please check that my assumptions are correct and compare databases sizes. It is possible that your new database is already filled with data from old one and you don't have to move anything. You can also test it on some cache table for small or medium texts and check does any translation was missing in new database. If you are using new database since beginning of 2017 it is possible that thanks to spiders all your old content is already translated. It is also possible that your forum is so big, that you are constantly run out of free translations quotas so new database is still not populated. It is wise to compare - even just by size. If new one is bigger, then it rather already has old texts,
    Last edited by vBET; 25-04-18 at 23:21.

  3. #3
    Member
    Join Date
    Aug 2010
    Posts
    73

    Default

    Hello!

    Thank you!
    The bases managed to merge correctly

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31