[Hibernate-JIRA] Created: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[Hibernate-JIRA] Created:...

Steve Ebersole (JIRA)

Monday, 9 August 2010 Mon, 9 Aug '10

12:23 p.m.

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.Beta3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Steve Ebersole (JIRA)

Monday, 9 August Mon, 9 Aug

12:28 p.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Description: ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.Beta3 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Steve Ebersole (JIRA)

2:24 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole commented on HHH-5452: ------------------------------------- Specifically for the intentions here I think we can limit this to UNIQUE and CHECK constraints (RI is the other category). Pretty trivial for UNIQUE constraints. The column variety: {code} create table XYZ ( ..., my_column UNIQUE ) {code} looks like the following: {code} create table XYZ ( ..., CONSTRAINT UNIQUE(my_column) ) {code} (note: ansi sql does say this form should name the constraint; need to see how enforced this is). Little more tricky for CHECK constraints. The column variety: {code} create table XYZ ( ..., my_column CHECK(in 'a', 'b') ) {code} needs to become: {code} create table XYZ ( ..., CONSTRAINT CHECK (my_column in 'a', 'b') ) {code} (note the injection of column name into the check condition; pretty sure blind prepend is ok here though).

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.Beta3 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

Steve Ebersole (JIRA)

Wednesday, 18 August Wed, 18 Aug

9:48 a.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Fix Version/s: (was: 3.6.0.Beta3) 3.6.0.Beta4

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.Beta4 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

Steve Ebersole (JIRA)

Tuesday, 31 August Tue, 31 Aug

1:30 p.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Fix Version/s: (was: 3.6.0.Beta4) cfg-rework

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: cfg-rework ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

Steve Ebersole (JIRA)

Wednesday, 13 October Wed, 13 Oct

9:31 p.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Fix Version/s: (was: cfg-rework) 4.0.0.Alpha1

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

Steve Ebersole (JIRA)

Friday, 4 March Fri, 4 Mar

3:55 p.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Fix Version/s: (was: 4.0.0.Alpha1) 4.0.0.Alpha2

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha2 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

Steve Ebersole (JIRA)

Thursday, 31 March Thu, 31 Mar

3:26 p.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Fix Version/s: (was: 4.0.0.Alpha2) 4.0.0.Alpha3

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

Steve Ebersole (JIRA)

Sunday, 24 April Sun, 24 Apr

9:06 a.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Fix Version/s: (was: 4.0.0.Alpha3) 4.0.0.Beta1

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Beta1 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

Steve Ebersole (JIRA)

Wednesday, 8 June Wed, 8 Jun

11:36 a.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Fix Version/s: (was: 4.0.0.Beta1) 4.1.0

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.1.0 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

Steve Ebersole (JIRA)

Tuesday, 27 December Tue, 27 Dec

12:06 p.m.

New subject: [Hibernate-JIRA] Updated: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452?page=c... ] Steve Ebersole updated HHH-5452: -------------------------------- Fix Version/s: (was: 4.1.0) 5.0.0

...

Account for dialects which expect check constraints on table definition as opposed to on column definition ---------------------------------------------------------------------------------------------------------- Key: HHH-5452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5452 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 5.0.0 ANSI SQL allows column constraints to be defined either on the table definition or on the column definition. Database dialects support varying degrees of that. We need to be able to account for both. Currently if we have constraints associated with the column in the metadata, and the dialect reports that it does not support constraints in the column definition we completely ignore them. Ideally if that is the case, but the dialect does support constraints in the table definition we should apply them there.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

4704

days inactive

5209

days old

hibernate-issues@lists.jboss.org

Manage subscription

10 comments

1 participants

tags (0)

participants (1)

Steve Ebersole (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[Hibernate-JIRA] Created: (HHH-5452) Account for dialects which expect check constraints on table definition as opposed to on column definition