Bug 1175910 - (6.3.z) HHH-6670, HHH-9500 - Errors when dropping contraints and tables that do not exist
Summary: (6.3.z) HHH-6670, HHH-9500 - Errors when dropping contraints and tables that ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Hibernate
Version: 6.3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.3.3
Assignee: Gail Badner
QA Contact: Martin Simka
URL:
Whiteboard:
Depends On: 1175388
Blocks: eap633-payload 1159890
TreeView+ depends on / blocked
 
Reported: 2014-12-18 20:59 UTC by Gail Badner
Modified: 2019-08-19 12:42 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1175388
Environment:
Last Closed: 2019-08-19 12:42:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Comment 2 Martin Simka 2015-01-28 13:13:24 UTC 
I've verified that errors [1] are no more present in the logs with fixes from HHH-9500 and HHH-6670.

commit from HHH-9545 seems to be additional commit for 4.3 and newer. There is no method supportsIfExistsBeforeConstraintName in Dialect in 4.2

[1]
13:23:40,964 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: drop sequence hibernate_sequence
13:23:40,964 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Sekvence "HIBERNATE_SEQUENCE" nenalezena

13:23:40,962 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: alter table Product_parts drop constraint FK_blj8umxx8k0105bye4jbx4c5y
13:23:40,963 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Tabulka "PRODUCT_PARTS" nenalezena
Comment 3 Gail Badner 2015-01-28 19:41:24 UTC 
Yes, that is correct. HHH-9545 is not present. Can we simply drop HHH-9545 from the list?
Comment 4 Gail Badner 2015-01-28 20:33:31 UTC 
Is QE the right person to answer, "Can we simply drop HHH-9545 from the list?."?
Note You need to log in before you can comment on or make changes to this bug.