Page MenuHomePhabricator

Sequence value update
Closed, DeclinedPublic

Description

Author: l.corsaro

Description:
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.


Version: unspecified
Severity: enhancement

Details

Reference
bz30544

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:52 PM
bzimport set Reference to bz30544.
bzimport added a subscriber: Unknown Object (MLST).

l.corsaro wrote:

SQL to update sequence actual value

Attached:

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?

l.corsaro wrote:

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.

Krinkle added a project: MediaWiki-Installer.
Krinkle subscribed.

Too little information to act on, and very old with no activity since. If this is still an issue, please file a new task.