Last modified: 2012-12-30 20:38:46 UTC
It's only a suggestion, could be useful during the update process of the update .php to cal allo a sql that set the actual value of each sequence to the last number in each table in this way we can avoi the annoying problem of duplicate key. Had happened to me a problem with the database that change the actual value of the sequence so I've written few lines of sql to update those. I hope can be usefuel alfo for others guy.
Created attachment 8969 [details] SQL to update sequence actual value
I assume this is some PostgreSQL or other non-MySQL issue that's specific to one or more particular database backends? What sort of situation do you find causes these incorrectly set sequence values you find? Is this a common problem? Could "fixing" the sequence values damage deliberate attempts to bump the sequences etc?
I assume this is some PostgreSQL or other non-MySQL issue that's specific to one or more particular database backends? Is related to postgres What sort of situation do you find causes these incorrectly set sequence values you find? I didn't investigate why but upgrade from 1.16 to 1.17 the sequence qher not to the exact value Is this a common problem? Could "fixing" the sequence values damage deliberate attempts to bump the sequences etc? No it doesn't bump other table beacause each sequence is used only on the related table.
