|
From: cremor (JIRA) <nh...@gm...> - 2010-09-29 06:03:46
|
Port support of unidirectional one-to-many with not nullable foreign key from Hibernate
---------------------------------------------------------------------------------------
Key: NH-2353
URL: http://216.121.112.228/browse/NH-2353
Project: NHibernate
Issue Type: Improvement
Components: Core
Affects Versions: 3.0.0.Alpha3
Reporter: cremor
Priority: Major
According to the following links, Hibernate supports unidirectional one-to-manys with not nullable foreign keys by specifying the key as nullable=false:
https://forum.hibernate.org/viewtopic.php?p=2408442#p2408442
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5091
Would be really nice if NHibernate would support that too. That way I could remove the references from child to parent entities in cases where the reference makes no sense in the domain model.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: cremor (JIRA) <nh...@gm...> - 2011-04-01 05:25:59
|
[ http://216.121.112.228/browse/NH-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20813#action_20813 ]
cremor commented on NH-2353:
----------------------------
I recently found that this is even documented in the Hibernate documentation:
http://docs.jboss.org/hibernate/core/3.6/reference/en-US/html/collections.html#collections-mapping
(In the red warning box if you scroll down a bit.)
And I also found a very old issue that basically describes the same improvement and is even the most voted open issue:
NH-1050
> Port support of unidirectional one-to-many with not nullable foreign key from Hibernate
> ---------------------------------------------------------------------------------------
>
> Key: NH-2353
> URL: http://216.121.112.228/browse/NH-2353
> Project: NHibernate
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.0.0.Alpha3
> Reporter: cremor
> Priority: Major
>
> According to the following links, Hibernate supports unidirectional one-to-manys with not nullable foreign keys by specifying the key as nullable=false:
> https://forum.hibernate.org/viewtopic.php?p=2408442#p2408442
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5091
> Would be really nice if NHibernate would support that too. That way I could remove the references from child to parent entities in cases where the reference makes no sense in the domain model.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-30 19:52:43
|
[ http://216.121.112.228/browse/NH-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-2353.
---------------------------
Resolution: Duplicate
Yes you are right, this is just a duplication of NH-1050.
Thanks.
> Port support of unidirectional one-to-many with not nullable foreign key from Hibernate
> ---------------------------------------------------------------------------------------
>
> Key: NH-2353
> URL: http://216.121.112.228/browse/NH-2353
> Project: NHibernate
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.0.0.Alpha3
> Reporter: cremor
> Priority: Major
>
> According to the following links, Hibernate supports unidirectional one-to-manys with not nullable foreign keys by specifying the key as nullable=false:
> https://forum.hibernate.org/viewtopic.php?p=2408442#p2408442
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5091
> Would be really nice if NHibernate would support that too. That way I could remove the references from child to parent entities in cases where the reference makes no sense in the domain model.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-30 19:57:55
|
[ http://216.121.112.228/browse/NH-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21237#action_21237 ]
Fabio Maulo commented on NH-2353:
---------------------------------
and lot of voters with ZERO test.
> Port support of unidirectional one-to-many with not nullable foreign key from Hibernate
> ---------------------------------------------------------------------------------------
>
> Key: NH-2353
> URL: http://216.121.112.228/browse/NH-2353
> Project: NHibernate
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.0.0.Alpha3
> Reporter: cremor
> Priority: Major
>
> According to the following links, Hibernate supports unidirectional one-to-manys with not nullable foreign keys by specifying the key as nullable=false:
> https://forum.hibernate.org/viewtopic.php?p=2408442#p2408442
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5091
> Would be really nice if NHibernate would support that too. That way I could remove the references from child to parent entities in cases where the reference makes no sense in the domain model.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|