[nhibernate-issues] [NHJIRA] Closed: (NH-823) Duplicate column names should generate NH exception, not ADO.NET

[Fabio M. (JIRA) <nh...@gm...>]

     [ http://216.121.112.228/browse/NH-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabio Maulo closed NH-823.
--------------------------

    Resolution: Not an Issue

As requested by reporter

> Duplicate column names should generate NH exception, not ADO.NET
> ----------------------------------------------------------------
>
>                 Key: NH-823
>                 URL: http://216.121.112.228/browse/NH-823
>             Project:  NHibernate
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.2.0.Beta2
>            Reporter: Andrés G. Aragoneses
>            Priority: Minor
>
> I have found that, if you have a mapping with duplicated name properties, such:
> <hibernate-mapping xmlns="urn:nhibernate-mapping-2.0" default-lazy="true">
>   <class name="Language, DataModel" table="IRM_LANGUAGES"
>          dynamic-update="true">
>     <id name="IdLanguage" column="IdLanguage" unsaved-value="0">
>       <generator class="native" />
>     </id>
>     <many-to-one name="Type" column="IdLanguage" not-null="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 warning the user about the wrong mapping file, the exception is thrown when the query is sent to the database.

-- 
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