From: NHibernate J. <mik...@us...> - 2006-11-27 10:02:31
|
Duplicate column names should generate NH exception, not ADO.NET ---------------------------------------------------------------- Key: NH-823 URL: http://jira.nhibernate.org/browse/NH-823 Project: NHibernate Type: Bug Versions: 1.2.0.Beta2 =20 Reporter: Andr=C3=A9s G. Aragoneses Priority: Trivial I have found that, if you have a mapping with duplicated name properties, s= uch: <hibernate-mapping xmlns=3D"urn:nhibernate-mapping-2.0" default-lazy=3D"tru= e"> <class name=3D"Language, DataModel" table=3D"IRM_LANGUAGES" dynamic-update=3D"true"> <id name=3D"IdLanguage" column=3D"IdLanguage" unsaved-value=3D"0"> <generator class=3D"native" /> </id> <many-to-one name=3D"Type" column=3D"IdLanguage" not-null=3D"true" /> </class> </hibernate-mapping> Here, there is a typo because the column of the many-to-one tag is the same= as the column of the ID. We have found that, in this case, instead of warn= ing the user about the wrong mapping file, the exception is thrown when the= query is sent to the database. --=20 This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nhibernate.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |