0001718: jpa: tries to create sequence that already exists

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0001718

[Resin]

minor

always

04-27-07 08:18

06-19-07 09:34

Reporter

sam

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

3.1.0

Summary

0001718: jpa: tries to create sequence that already exists

Description

The application has <create-database-schema> true, the tables already exist, the first attempt to do an update in a transaction fails because Amber tries to create the sequence that already exists.

[11:15:21.472] jdbc/recipes.1.9:createStatement()
[11:15:21.521] jdbc/recipes.1.9:exn-executeUpdate(CREATE SEQUENCE categories_cseq INCREMENT 50) -> org.postgresql.util.PSQLException: ERROR: relation "categories_cseq" already exists
[11:15:21.521] jdbc/recipes.1.9:close()
[11:15:21.521] jdbc/recipes.1.10:prepareStatement(SELECT Nextval('categories_cseq'))
[11:15:21.523] jdbc/recipes.1.10:executeQuery(SELECT Nextval('categories_cseq'))
[11:15:21.524] jdbc/recipes.1.10:exn-executeQuery(org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block)

Additional Information

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
04-27-07 08:18	sam	New Issue
06-19-07 09:34	ferg	Assigned To	=> ferg
06-19-07 09:34	ferg	Status	new => closed
06-19-07 09:34	ferg	Resolution	open => fixed
06-19-07 09:34	ferg	Fixed in Version	=> 3.1.2

Mantis 1.0.0rc3[^]

27 total queries executed.
25 unique queries executed.