| Type: Bug Reoprt | Version: 2.9.4 | Priority: Critical | Status: Closed | Replies: 2 |
at a customer the unique object id of one class changed dramatically from a nurmal number to an incredible number which, for sure, cannot be used any more, see screenshot
the database is available here
https://www.dropbox.com/scl/fi/564zgf7ubm1yh6kp2wxoi/coreSystemDb.7z?rlkey=x66xs7kr893ekbxz51rvfj9ne&dl=0
This is indeed very strange, and apparently the first report of such an issue. Theoretically, this may be caused by a loop that allocates IDs and does not use them or creates objects and then deletes them, but the gap is too large to believe that this is what happened. At this point there is no path to fix anything as there is insufficient information to understand the cause.
No special problems can be observed in the database, which seems to be functional, except that the automatic ID generator that is used for some of the entity classes jumped unexpectedly. Therefore, although the numbers are very large and strange, it is unclear why they cannot be used, unless you need them in a user interface that expects shorter numbers.
There is no quick solution for updating the IDs as IDs are fixed once set. Fixing the database may require creating a new database and copying the content of this database to a new database, using a custom program.
ok, the problem with the long number that became unusable was internal (conversion of the longint from JSON to Java), we can close the post
