Defect #198

id sequence fails after trac import

Added by Panta Rhei about 14 years ago. Updated about 14 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution: Affected version:

Description

after a trac import adding a new issue failed cause the 'issue_id_seq' started at 1 albeit the id 1 was taken by the
import. would be a bigger problem if the imported trac tickets are starting at 4000 eg. 4000 new tickets will be ok
in redmine. ticket 4001 breaks the app.

setting the correct nextval in the db fixed the issue.

i'm using postgresql. but i think is an db independent problem.

History

#1 Updated by Jean-Philippe Lang about 14 years ago

Fixed in r1099. The sequence is now properly updated when using
postgres.

#2 Updated by Panta Rhei about 14 years ago

No. It works fine with mysql.
But I'll try to find a solution to this problem.

Ok. Great news. Thx for all your work. :)

#3 Updated by Jean-Philippe Lang about 14 years ago

but i think is an db independent problem.

No. It works fine with mysql.
But I'll try to find a solution to this problem.

Also available in: Atom PDF