6:03 p.m.
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
8:05 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Christian Bauer commented on ANN-598:
-------------------------------------
Note that @OnDelete and the core feature <key on-delete> is not enough: I need these
options for all foreign keys (including secondary tables) and I need not only CASCADE but
also SET NULL.
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
9:27 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Max Rydahl Andersen commented on ANN-598:
-----------------------------------------
isn't this where we would normally post something like: "we can't cover every
forseeable schema creation/sql dml construct in shcemaexport/update..." and then
reject it :)
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
9:30 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Max Rydahl Andersen commented on ANN-598:
-----------------------------------------
btw. not sure all db's are much in sync on syntax nor semantics capabilities of these
+ on what sequence should be used for dropping (in other words: it's not trivial to
implement reliable/portable)
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
10:59 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Christian Bauer commented on ANN-598:
-------------------------------------
That's why I want schema export to do it, it can't be that hard to add SET NULL in
addition to the CASCADE option we already have.
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
11:47 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Arik Kfir commented on ANN-598:
-------------------------------
Actually, this is a very common scenario. Often, a database is updated both by the
application code, and by some other legacy application/DBA/programmers/etc and by using
the database to do the "SET NULL" behavior, one gets a consistent behavior
across all database users (be them Hibernate, legacy app, etc).
Right now, as the issue poster says, the programmers have to either code the behavior in
code, or alter the schema. Both solutions leave something to be desired...
+1 from me.
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
3 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Peter Royle commented on ANN-598:
---------------------------------
by using the database to do the "SET NULL" behaviour, one
gets a consistent behaviour across all database users (be them Hibernate, legacy app,
etc).
Maybe you're right, but unless something's changed since about 3.2.0, I found that
purely using SET NULL in the database left Hibernate squarely out of the loop (the
Hibernate cache would have no idea that the effected association had been nullified). We
still need a way of informing the Hibernate cache that a particular association will
be/has been nullified in the database as a result of deleting the associated entity. The
simplistic approach I implemented was to simply evict the associated entity from the
cache.
For stand-alone Hibernate applications I think the best we can hope for is to be able to
implement this in a way which is consistent across a single instance of the application,
the DB and any other applications which use the same database but don't heavily cache
entity state. Any other instances of applications which heavily cache entity state will be
left in the dark.
I think however that when it comes to using JPA within an application server the
consistency may be able to spread across all applications deployed on that (cluster of)
application server, if they can all be configured to utilise the same cache. Not entirely
sure about that one though. Anyone an expert on this?
Pete.
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
3:39 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Christian Bauer commented on ANN-598:
-------------------------------------
Obviously instances in the current persistence context would be invalid after such a
database side-effect of cascading. Which doesn't matter in most cases, because
deletion happens just before the persistence context is closed anyway (in web
conversations with persistence-context-per-conversation this is the normal pattern). The
second-level cache obviously needs to be disabled for such entity associations.
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
8:50 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Arik Kfir commented on ANN-598:
-------------------------------
Indeed.
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
2:13 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Daniel Jimenez commented on ANN-598:
------------------------------------
+1 from me as well.
All of our users from the "users" table have FKs to a few other tables. In most
cases if the row in the other table is deleted we obviously would not want the whole user
deleted, instead just that field set to null. As an example, you would not want a user
deleted just because their default checking account was deleted in another table. Instead
you'd rather set their default checking account to null, because they may have a
savings account, CD, money market, etc.
I quickly looked over the source for the OnDelete and OnDeleteAction annotations, which
led me to AnnotationBinder. Having never looked at any of the Hibernate source before, I
very quickly got overwhelmed.
Daniel
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
4:39 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-598) Add ON clause to @ForeignKey
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-598?page=co...
]
Daniel Jimenez commented on ANN-598:
------------------------------------
I believe this needs to depend on:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2707
Add ON clause to @ForeignKey
----------------------------
Key: ANN-598
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Reporter: Christian Bauer
More important than it sounds:
@org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID")
I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via:
<hibernate-mapping>
<database-object>
<create>
alter table FEED drop constraint FK_FEED_DIRECTORY_ID;
alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key
(DIRECTORY_ID) references NODE on delete cascade;
</create>
<drop></drop>
</database-object>
</hibernate-mapping>
This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an
option - I don't want to hardcode my HSQL datatypes.
So we should accept a parameter on @ForeignKey (I know that the Hibernate binder
doesn't have that notion at all, we need it in native Hibernate as well) that accepts
"[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right
thing during schema export.
--
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
5528
days inactive
6277
days old
hibernate-issues@lists.jboss.org
10 comments
5 participants
participants (5)
-
Arik Kfir (JIRA) -
Christian Bauer (JIRA)
-
Daniel Jimenez (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Peter Royle (JIRA)