1. Seppi
  2. RO CSVI
  3. Monday, 17 February 2025
  4.  Subscribe via email
Hi Tharuna

Concerning our ID shifting challenge... (should we maybe move this into news ticket?).

Rolands approach with keeping the IDs on importing seems really a good one. Since the new environment (where we import) was a clone of the source environment (where we export), the IDs are partially identical, but split after we did the first import (and the customer creates new articles in both environments). So we will run into an ID collision sooner or later...

As I wrote in my previous post, our idea was therefore, shifting the IDs of the existing content in the import environment to a massively higher value (so all newly created articles in the new environment are «miles away» of the IDs we could ever import from the source environment). With our mySQL trials (meaning: Claude & ChatGPT, which both seem rather «retarded» when it comes to joomla 5) we manage to do the shift, but we only get empty articles listing in the backend, however.

Now, we hope ROCSVI can help us with this. The plan is as follows:

1. exporting everything in the target (import) environment (without the articles we need to import from the source environment)
2. Shift the ID auto increment id initial value to 20000 in MySQL
3. Delete all ids in our export file
4. Import the file (all articles are getting IDs higher than 20000)
5. Import the articles from the source environment (with the old ids in the 1000 range)

Could this work (are all links to custom fields, categories etc. surviving this procedure)? Or do you have a better approach?

Thank you so much

Peter
Sorry, the discussion is currently locked. You will not be able to post a reply or a comment at the moment.