Menu
▾
▴
nhibernate-issues — Updates to JIRA issues are sent to this list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(110) |
Nov
(296) |
Dec
(107) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(212) |
Feb
(263) |
Mar
(161) |
Apr
(183) |
May
(183) |
Jun
(75) |
Jul
(106) |
Aug
(88) |
Sep
(227) |
Oct
(143) |
Nov
(154) |
Dec
(53) |
| 2008 |
Jan
(77) |
Feb
|
Mar
|
Apr
(6) |
May
(103) |
Jun
(296) |
Jul
(54) |
Aug
|
Sep
(379) |
Oct
(283) |
Nov
(224) |
Dec
(214) |
| 2009 |
Jan
(129) |
Feb
(257) |
Mar
(136) |
Apr
(12) |
May
(329) |
Jun
(434) |
Jul
(375) |
Aug
(171) |
Sep
|
Oct
|
Nov
|
Dec
(54) |
| 2010 |
Jan
(198) |
Feb
(76) |
Mar
(3) |
Apr
(1) |
May
|
Jun
(62) |
Jul
(210) |
Aug
(447) |
Sep
(330) |
Oct
(257) |
Nov
(133) |
Dec
(453) |
| 2011 |
Jan
(240) |
Feb
(128) |
Mar
(442) |
Apr
(320) |
May
(428) |
Jun
(141) |
Jul
(13) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: NHibernate J. <mik...@us...> - 2007-01-04 14:01:37
|
[ http://jira.nhibernate.org/browse/NH-216?page=comments#action_14721 ] Sergey Koshcheyev commented on NH-216: -------------------------------------- Actually, I don't see the reason for throwing a different exception here - the problem is really a security issue, not a mapping one. And I believe you can find out what the problem is from the stack trace. > NHibernate should test for Reflection permission and failover if not present > ---------------------------------------------------------------------------- > > Key: NH-216 > URL: http://jira.nhibernate.org/browse/NH-216 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2, beta-0.7 > Reporter: Paul Hatcher > Assignee: Paul Hatcher > Fix For: 1.2.0.Beta3 > > Currently, Hibernate uses Reflection without checking for permission, this causes SecurityExceptions on ASP.NET servers set to Medium security. > What we should do is check for Reflection permission and raise a MappingException if we do not have it and we are being asked to access other than via public properties/fields. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-04 11:29:34
|
[ http://jira.nhibernate.org/browse/NH-850?page=all ] Sergey Koshcheyev closed NH-850: -------------------------------- Resolution: Fixed > Non-portable file path for generated source files by hbm2net > ------------------------------------------------------------ > > Key: NH-850 > URL: http://jira.nhibernate.org/browse/NH-850 > Project: NHibernate > Type: Bug > Components: Contrib > Versions: 1.0.3 > Reporter: Sebastian Brady > Priority: Minor > Fix For: 1.2.0.Beta3 > > NHibernate.Tools.hbm2net uses non-portable path names for the files it generates. The hardcoded path separator ("\") won't work on Unix-like systems. > The System.IO.Path methods should be used to build the path name. > Suggest that in the NHibernate.Tool.hbm2net.Generator.write() method (file: src/NHibernate.Tool.hbm2net/Generator.cs, line 152) > FileInfo file = new FileInfo(dir.FullName + "\\" + this.getFileName(saveToClassName)); > becomes > FileInfo file = new FileInfo(System.IO.Combine(dir.FullName, this.getFileName(saveToClassName)); > And, in NHibernate.Tool.hbm2net.Generator.getDir() method (line 203) > dir = new FileInfo(baseDir.FullName + "\\" + p.Replace(StringHelper.Dot, Path.DirectorySeparatorChar)); > becomes > dir = new FileInfo(System.IO.Combine(baseDir.FullName, > p.Replace(StringHelper.Dot, Path.DirectorySeparatorChar))); -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-04 10:43:35
|
[ http://jira.nhibernate.org/browse/NH-851?page=all ] Sergey Koshcheyev updated NH-851: --------------------------------- Fix Version: 1.2.0.Beta3 Version: 1.2.0.Beta2 > More descriptive error message for 'Cannot find constructor' on projections > --------------------------------------------------------------------------- > > Key: NH-851 > URL: http://jira.nhibernate.org/browse/NH-851 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Ken Egozi > Priority: Trivial > Fix For: 1.2.0.Beta3 > Attachments: DisplayParametersOnConstructorNotFound.patch > > Using .NET 2.0, over SQL Server 2005 > one of the latests changes (I guess) was that "select new Projection(... sum(s.Data)) ... " would assume "long" for the sum element, rather than int. > So if the projection has "int" in the constructor an exception will occur. > However, current users gets a non informative error message. > attached here a patch that would add the expected types for the contructor's parameters, so it would be easier to fix. > I was not able to build the solution due to some local problems with nant, so it should be tested. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-04 10:39:34
|
[ http://jira.nhibernate.org/browse/NH-845?page=all ] Sergey Koshcheyev closed NH-845: -------------------------------- Resolution: Fixed > Queries and imports in separate hmb.xml are not parsed (re-opening) > ------------------------------------------------------------------- > > Key: NH-845 > URL: http://jira.nhibernate.org/browse/NH-845 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0.2 > Reporter: Jon Resnick > Priority: Minor > Fix For: 1.2.0.Beta3 > > This issue was originally posted as NH-542 and then closed. However the issue is real, as of 1.0.2. The problem occurs because the class NHibernate.Cfg.AssemblyHbmOrderer discards any mapping files that do not contain a "class" or "joined-subclass" or "subclass" element. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-04 10:14:33
|
[ http://jira.nhibernate.org/browse/NH-851?page=comments#action_14720 ] Ken Egozi commented on NH-851: ------------------------------ More info at can be found at http://www.kenegozi.com/blog/2007/01/04/NHibernateCouldNotFindConstructorForInSelectNewProjectionQuery.aspx > More descriptive error message for 'Cannot find constructor' on projections > --------------------------------------------------------------------------- > > Key: NH-851 > URL: http://jira.nhibernate.org/browse/NH-851 > Project: NHibernate > Type: Improvement > Components: Core > Reporter: Ken Egozi > Priority: Trivial > Attachments: DisplayParametersOnConstructorNotFound.patch > > Using .NET 2.0, over SQL Server 2005 > one of the latests changes (I guess) was that "select new Projection(... sum(s.Data)) ... " would assume "long" for the sum element, rather than int. > So if the projection has "int" in the constructor an exception will occur. > However, current users gets a non informative error message. > attached here a patch that would add the expected types for the contructor's parameters, so it would be easier to fix. > I was not able to build the solution due to some local problems with nant, so it should be tested. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-04 10:07:35
|
More descriptive error message for 'Cannot find constructor' on projections
---------------------------------------------------------------------------
Key: NH-851
URL: http://jira.nhibernate.org/browse/NH-851
Project: NHibernate
Type: Improvement
Components: Core
Reporter: Ken Egozi
Priority: Trivial
Attachments: DisplayParametersOnConstructorNotFound.patch
Using .NET 2.0, over SQL Server 2005
one of the latests changes (I guess) was that "select new Projection(... sum(s.Data)) ... " would assume "long" for the sum element, rather than int.
So if the projection has "int" in the constructor an exception will occur.
However, current users gets a non informative error message.
attached here a patch that would add the expected types for the contructor's parameters, so it would be easier to fix.
I was not able to build the solution due to some local problems with nant, so it should be tested.
--
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
|
|
From: NHibernate J. <mik...@us...> - 2007-01-03 14:31:26
|
[ http://jira.nhibernate.org/browse/NH-842?page=all ] Sergey Koshcheyev closed NH-842: -------------------------------- Fix Version: (was: 1.2.0.Beta3) Resolution: Won't Fix Worked for me in Beta3, will not fix it in 1.0.x. > Generated SQL column name aliased wrong? > ---------------------------------------- > > Key: NH-842 > URL: http://jira.nhibernate.org/browse/NH-842 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0.2, 1.0.3 > Reporter: Ka Man Tong > Attachments: Account-orig.hbm.xml, Account.cs, Account.hbm.xml > > I have over 200 fields defined for a table accessing MSSQL 2000. > Some fields have similar prefix (accountId, accountNumber, accountCategoryCode, etc) and I can see NHibernate generate the retrival SQL using the same prefix with some additional numbers and underscore as the column alias. > All fields are in Int32, except one which is of String type. > When retrieving, I got Number Format Exception when NHibernate tries to read some Int32 fields. As I suspect that it was the Nullable issues and I have changed all Int32 fields to NullableInt32. However the case is still the same. > The field mapping XML is defined without any particular order of the fields. > But when I tried to group all AccountXXX fields at the top of the mapping XML, the Number Format Exception doesn't appear anymore. > Is the field mapping ordering important? -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-03 14:02:31
|
[ http://jira.nhibernate.org/browse/NH-693?page=all ] Sergey Koshcheyev updated NH-693: --------------------------------- Fix Version: (was: 1.2.0.Beta3) LATER Postponing since I'm not sure what the best fix would be and since this doesn't look important. > Better error message when user forgets to supply table name > ----------------------------------------------------------- > > Key: NH-693 > URL: http://jira.nhibernate.org/browse/NH-693 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Dru Sellers > Priority: Minor > Fix For: LATER > > Can we have better error msg for this error? > "NHibernate.MappingException: Index was outside the bounds of the array. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array. > at NHibernate.Mapping.Table.set_Name(String value) > at NHibernate.Cfg.Mappings.AddTable(String schema, String name) > at NHibernate.Cfg.Binder.BindRootClass(XmlNode node, RootClass model, Mappings mappings) > at NHibernate.Cfg.Binder.BindRoot(XmlDocument doc, Mappings model) > at NHibernate.Cfg.Configuration.AddValidatedDocument(XmlDocument doc) > at NHibernate.Cfg.Configuration.AddXmlReader(XmlTextReader hbmReader) > at NHibernate.Cfg.Configuration.AddInputStream(Stream xmlInputStream) > --- End of inner exception stack trace --- > at NHibernate.Cfg.Configuration.AddInputStream(Stream xmlInputStream) > at NHibernate.Cfg.Configuration.AddAssembly(Assembly assembly, Boolean skipOrdering) > at NHibernate.Cfg.Configuration.AddAssembly(Assembly assembly) > at NHibernate.Cfg.Configuration.AddAssembly(String assemblyName) > I would be happy to code it up, but not sure where to best put the check? > NHibernate.Mapping.Table.set_Name (least amount of code repeat.) > or > NHibernate.Cfg.Mappings.AddTable(String schema, String name) best place to provide the most info possible. Actually this is a bad place too. > --Thoughts?-- -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-03 11:40:28
|
[ http://jira.nhibernate.org/browse/NH-826?page=all ] Sergey Koshcheyev closed NH-826: -------------------------------- Resolution: Fixed > Using Criteria to query for an item throws on Flush in some situations > ---------------------------------------------------------------------- > > Key: NH-826 > URL: http://jira.nhibernate.org/browse/NH-826 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Aaron Jensen > Fix For: 1.2.0.Beta3 > Attachments: NH826.patch, NHibernateTest.zip > > The situation is best described by the attached sample project, but I will attempt to explain in words when this problem occurs. > EntityA has a many-to-many to EntityB > EntityB has a subclass EntityC > EntityC has a one-to-many to EntityD > If you create an EntityB and associate it to EntityA, then query for EntityA via Criteria (but not via HQL) then Session.Flush() will fail with: > NHibernate.HibernateException: You may not dereference an collection with cascade="all-delete-orphan" > at NHibernate.Impl.SessionImpl.UpdateUnreachableCollection(IPersistentCollection coll) in c:\net\nhibernate\nhibernat > e\src\NHibernate\Impl\SessionImpl.cs:line 3957 > at NHibernate.Impl.SessionImpl.FlushCollections() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs: > line 3802 > at NHibernate.Impl.SessionImpl.FlushEverything() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:l > ine 3090 > The collection it is complaining about is a collection of EntityD objects which should never have been created in the first place. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 18:46:29
|
[ http://jira.nhibernate.org/browse/NH-823?page=3Dcomments#action_1470= 4 ] =20 Sergey Koshcheyev commented on NH-823: -------------------------------------- Yes, the check was only done for columns that didn't have insert=3D"false" = update=3D"false". > 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 > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Andr=C3=A9s G. Aragoneses > Priority: Trivial > Fix For: 1.2.0.Beta3 > > I have found that, if you have a mapping with duplicated name properties,= such: > <hibernate-mapping xmlns=3D"urn:nhibernate-mapping-2.0" default-lazy=3D"t= rue"> > <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 sa= me as the column of the ID. We have found that, in this case, instead of wa= rning the user about the wrong mapping file, the exception is thrown when t= he 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 17:06:29
|
[ http://jira.nhibernate.org/browse/NH-823?page=3Dcomments#action_1470= 3 ] =20 Ayende Rahien commented on NH-823: ---------------------------------- There are valid reasons to want to map the same column to different propert= ies. Usually this is a case where the id of an object is meaningful. For instance, you may have Employee assoication, but also EmployeeId proper= ty. > 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 > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Andr=C3=A9s G. Aragoneses > Priority: Trivial > Fix For: 1.2.0.Beta3 > > I have found that, if you have a mapping with duplicated name properties,= such: > <hibernate-mapping xmlns=3D"urn:nhibernate-mapping-2.0" default-lazy=3D"t= rue"> > <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 sa= me as the column of the ID. We have found that, in this case, instead of wa= rning the user about the wrong mapping file, the exception is thrown when t= he 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 14:44:24
|
[ http://jira.nhibernate.org/browse/NH-840?page=all ] Sergey Koshcheyev closed NH-840: -------------------------------- Resolution: Fixed > Include Inner Exception on 'Duplicate identifier in table for:' exception msg > ------------------------------------------------------------------------------ > > Key: NH-840 > URL: http://jira.nhibernate.org/browse/NH-840 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Shane Walters > Priority: Minor > Fix For: 1.2.0.Beta3 > > Using: > NHibernate 1.2.Beta2 > DotNet 2.0 > MS Sql Server 2000 > I encountered the following error in 1.2 Beta 2. > NHibernate.HibernateException: Duplicate identifier in table for: [Singletree.Core.Domain.Folder#89193] > at NHibernate.Persister.Entity.AbstractEntityPersister.Check(Int32 rows, Object id, Int32 tableNumber, IExpectation expectation, IDbCommand statement) > at NHibernate.Persister.Entity.AbstractEntityPersister.Update(Object id, Object[] fields, Object[] oldFields, Boolean[] includeProperty, Int32 j, Object oldVersion, Object obj, SqlCommandInfo sql, ISessionImplementor session) > at NHibernate.Persister.Entity.AbstractEntityPersister.Update(Object id, Object[] fields, Int32[] dirtyFields, Boolean hasDirtyCollection, Object[] oldFields, Object oldVersion, Object obj, ISessionImplementor session) > at NHibernate.Impl.ScheduledUpdate.Execute() > at NHibernate.Impl.SessionImpl.Execute(IExecutable executable) > at NHibernate.Impl.SessionImpl.ExecuteAll(IList list) > at NHibernate.Impl.SessionImpl.Execute() > Took me the better part of a day to figure out that I had a trigger which was affecting the row count. If the TooManyRowsAffectedException is passed to MessageHelper.InfoString, then we get a message that makes it much easier to determine what is happening. > In NHibernate.Persister.Entity.AbstractEntityPersister.Check(int rows, object id, int tableNumber, IExpectation expectation, IDbCommand statement) > catch (TooManyRowsAffectedException ex) > { > throw new HibernateException( > "Duplicate identifier in table for: " + > MessageHelper.InfoString(this, id, Factory),ex); > } > Now we get a better msg: > NHibernate.HibernateException: Duplicate identifier in table for: [Singletree.Webpdm.Core.Domain.Folder#89193] ---> NHibernate.AdoNet.TooManyRowsAffectedException: Unexpected row count: 2; expected: 1 -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 14:30:22
|
[ http://jira.nhibernate.org/browse/NH-837?page=all ] Sergey Koshcheyev closed NH-837: -------------------------------- Resolution: Fixed > Error using Limits with DB2400Dialect > ------------------------------------- > > Key: NH-837 > URL: http://jira.nhibernate.org/browse/NH-837 > Project: NHibernate > Type: Bug > Components: Data Providers > Versions: 1.2.0.Beta2 > Reporter: Christophe Vigouroux > Priority: Minor > Fix For: 1.2.0.Beta3 > > Using with DB2400Dialect : > query.SetFirstResult(startRow); > query.SetMaxResults(maxRows); > IList<Core.Imprimante> retour = query.List<Core.Imprimante>(); > results in the generation of the following SQL statement : > select * from (select rownumber() over() as rownum, this_.CDIMPLOG as CDIMPLOG0_0_, this_.CDSOC as CDSOC0_0_, this_.LBIMP as LBIMP0_0_ FROM TIMPRIM this_) as tempresult where rownum <= ? > This statement is for use with DB2 UDB, but not compatible with DB2 for iSeries. > The statement should use RRN(table) instead of rownumber() and use "fetch first n rows" instead of over(). > DB2400Dialect should override GetLimitString of DB2Dialect to provide with functionality. > Thanks for your support ! -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 13:32:27
|
[ http://jira.nhibernate.org/browse/NH-823?page=3Dcomments#action_1470= 2 ] =20 Sergey Koshcheyev commented on NH-823: -------------------------------------- The check was there before but was removed since H3 doesn't do it. I don't = remember the reason now, need to investigate further. > 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 > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Andr=C3=A9s G. Aragoneses > Priority: Trivial > Fix For: 1.2.0.Beta3 > > I have found that, if you have a mapping with duplicated name properties,= such: > <hibernate-mapping xmlns=3D"urn:nhibernate-mapping-2.0" default-lazy=3D"t= rue"> > <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 sa= me as the column of the ID. We have found that, in this case, instead of wa= rning the user about the wrong mapping file, the exception is thrown when t= he 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 11:27:27
|
[ http://jira.nhibernate.org/browse/NH-839?page=all ] Sergey Koshcheyev closed NH-839: -------------------------------- Resolution: Fixed > PersistentGenericMap GetSnapshotElement InvalidCastException > ------------------------------------------------------------ > > Key: NH-839 > URL: http://jira.nhibernate.org/browse/NH-839 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Sergey Koshcheyev > Priority: Trivial > Fix For: 1.2.0.Beta3 > Attachments: PersistentGenericMap.cs > > http://forum.hibernate.org/viewtopic.php?p=2334749#2334749 -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 10:17:28
|
[ http://jira.nhibernate.org/browse/NH-841?page=all ] Sergey Koshcheyev updated NH-841: --------------------------------- Fix Version: 1.2.0.Beta3 > generator class="native" not works with NHibernate.JetDriver > ------------------------------------------------------------ > > Key: NH-841 > URL: http://jira.nhibernate.org/browse/NH-841 > Project: NHibernate > Type: Bug > Components: Contrib > Versions: 1.2.0.Beta2 > Reporter: Sergio > Priority: Minor > Fix For: 1.2.0.Beta3 > Attachments: BUGAccess.rar > > If you have define the id with a autonumeric and use generator class="native" when save the following mistake happens: "null id in entry (don't flush the Session after an exception occurs)". > If use generator class="increment" it works well. > I dont know if is normal or a bug, but is not nice if you use the same mapping files with access and sql server. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 10:13:24
|
[ http://jira.nhibernate.org/browse/NH-847?page=all ] Sergey Koshcheyev updated NH-847: --------------------------------- Fix Version: LATER > Oracle stored procedure with Ref Cursor out > ------------------------------------------- > > Key: NH-847 > URL: http://jira.nhibernate.org/browse/NH-847 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Brian Choi > Priority: Critical > Fix For: LATER > > http://forum.hibernate.org/viewtopic.php?t=968269 -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 10:11:24
|
[ http://jira.nhibernate.org/browse/NH-850?page=all ] Sergey Koshcheyev updated NH-850: --------------------------------- Fix Version: 1.2.0.Beta3 > Non-portable file path for generated source files by hbm2net > ------------------------------------------------------------ > > Key: NH-850 > URL: http://jira.nhibernate.org/browse/NH-850 > Project: NHibernate > Type: Bug > Components: Contrib > Versions: 1.0.3 > Reporter: Sebastian Brady > Priority: Minor > Fix For: 1.2.0.Beta3 > > NHibernate.Tools.hbm2net uses non-portable path names for the files it generates. The hardcoded path separator ("\") won't work on Unix-like systems. > The System.IO.Path methods should be used to build the path name. > Suggest that in the NHibernate.Tool.hbm2net.Generator.write() method (file: src/NHibernate.Tool.hbm2net/Generator.cs, line 152) > FileInfo file = new FileInfo(dir.FullName + "\\" + this.getFileName(saveToClassName)); > becomes > FileInfo file = new FileInfo(System.IO.Combine(dir.FullName, this.getFileName(saveToClassName)); > And, in NHibernate.Tool.hbm2net.Generator.getDir() method (line 203) > dir = new FileInfo(baseDir.FullName + "\\" + p.Replace(StringHelper.Dot, Path.DirectorySeparatorChar)); > becomes > dir = new FileInfo(System.IO.Combine(baseDir.FullName, > p.Replace(StringHelper.Dot, Path.DirectorySeparatorChar))); -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 10:00:23
|
[ http://jira.nhibernate.org/browse/NH-845?page=all ] Sergey Koshcheyev updated NH-845: --------------------------------- Fix Version: 1.2.0.Beta3 > Queries and imports in separate hmb.xml are not parsed (re-opening) > ------------------------------------------------------------------- > > Key: NH-845 > URL: http://jira.nhibernate.org/browse/NH-845 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0.2 > Reporter: Jon Resnick > Priority: Minor > Fix For: 1.2.0.Beta3 > > This issue was originally posted as NH-542 and then closed. However the issue is real, as of 1.0.2. The problem occurs because the class NHibernate.Cfg.AssemblyHbmOrderer discards any mapping files that do not contain a "class" or "joined-subclass" or "subclass" element. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 10:00:23
|
[ http://jira.nhibernate.org/browse/NH-849?page=all ] Sergey Koshcheyev closed NH-849: -------------------------------- Resolution: Not an Issue > MIN()- and MAX()-projections > ---------------------------- > > Key: NH-849 > URL: http://jira.nhibernate.org/browse/NH-849 > Project: NHibernate > Type: New Feature > Components: Data Providers > Versions: 1.2.0.Beta2 > Reporter: Erik Meusel > Priority: Minor > Attachments: MinMax.tar.gz > > I wrote two small and missing projections for MIN() and MAX() for my NHibernate application and would like to write at least another one for CAST(). I'll attach the first two, just in case you're interested in them (since they are really small and not quite complicated to implement at all). -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 09:34:23
|
[ http://jira.nhibernate.org/browse/NH-838?page=all ] Sergey Koshcheyev updated NH-838: --------------------------------- Fix Version: LATER > nosetter access strategy on <version> tag causes incorrect dirty check result > ----------------------------------------------------------------------------- > > Key: NH-838 > URL: http://jira.nhibernate.org/browse/NH-838 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Bill Poole > Priority: Minor > Fix For: LATER > > Applying the "nosetter" property access strategy on the <version> element in a mapping file for an entity type seems to cause NHibernate to falsely detect a dirty condition for any entity instance of that type and issue an UPDATE against the database. > Changing the access strategy to "field" immediately caused the UPDATEs no longer to be issued against the database. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 09:34:23
|
[ http://jira.nhibernate.org/browse/NH-846?page=all ] Sergey Koshcheyev closed NH-846: -------------------------------- Resolution: Won't Fix 1.0.x is not developed any more and it does not support .NET 2.0 so I'm not going to fix this. > Support Sqlite ADO.Net 2.0 DataProvider for Nhibernate 1.0.3 > ------------------------------------------------------------ > > Key: NH-846 > URL: http://jira.nhibernate.org/browse/NH-846 > Project: NHibernate > Type: Patch > Components: Data Providers > Versions: 1.0.3 > Reporter: Bertrand LEGA > Priority: Trivial > Attachments: NHibernate.SQLite20.zip > > NHibernate ist compiled against the old version of the SQLite ADO.Net Provider. But this Provider isnt updated since Feb. 2005. > The newer one only supports Ado.Net 2.0. You can find it on http://sourceforge.net/projects/sqlite-dotnet2 . > Enclosed a SVN Patch that uses the Ado.Net 2.0 Version if NHibernate isn't compiled with .Net 1.0 1.1 or Mono 1.0. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 09:32:28
|
[ http://jira.nhibernate.org/browse/NH-846?page=all ] Sergey Koshcheyev updated NH-846: --------------------------------- Version: (was: 1.2.0.Beta1) 1.0.3 > Support Sqlite ADO.Net 2.0 DataProvider for Nhibernate 1.0.3 > ------------------------------------------------------------ > > Key: NH-846 > URL: http://jira.nhibernate.org/browse/NH-846 > Project: NHibernate > Type: Patch > Components: Data Providers > Versions: 1.0.3 > Reporter: Bertrand LEGA > Priority: Trivial > Attachments: NHibernate.SQLite20.zip > > NHibernate ist compiled against the old version of the SQLite ADO.Net Provider. But this Provider isnt updated since Feb. 2005. > The newer one only supports Ado.Net 2.0. You can find it on http://sourceforge.net/projects/sqlite-dotnet2 . > Enclosed a SVN Patch that uses the Ado.Net 2.0 Version if NHibernate isn't compiled with .Net 1.0 1.1 or Mono 1.0. -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 09:32:28
|
[ http://jira.nhibernate.org/browse/NH-840?page=all ] Sergey Koshcheyev updated NH-840: --------------------------------- Fix Version: 1.2.0.Beta3 Version: (was: 1.2.0.Beta3) (was: LATER) 1.2.0.Beta2 > Include Inner Exception on 'Duplicate identifier in table for:' exception msg > ------------------------------------------------------------------------------ > > Key: NH-840 > URL: http://jira.nhibernate.org/browse/NH-840 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Shane Walters > Priority: Minor > Fix For: 1.2.0.Beta3 > > Using: > NHibernate 1.2.Beta2 > DotNet 2.0 > MS Sql Server 2000 > I encountered the following error in 1.2 Beta 2. > NHibernate.HibernateException: Duplicate identifier in table for: [Singletree.Core.Domain.Folder#89193] > at NHibernate.Persister.Entity.AbstractEntityPersister.Check(Int32 rows, Object id, Int32 tableNumber, IExpectation expectation, IDbCommand statement) > at NHibernate.Persister.Entity.AbstractEntityPersister.Update(Object id, Object[] fields, Object[] oldFields, Boolean[] includeProperty, Int32 j, Object oldVersion, Object obj, SqlCommandInfo sql, ISessionImplementor session) > at NHibernate.Persister.Entity.AbstractEntityPersister.Update(Object id, Object[] fields, Int32[] dirtyFields, Boolean hasDirtyCollection, Object[] oldFields, Object oldVersion, Object obj, ISessionImplementor session) > at NHibernate.Impl.ScheduledUpdate.Execute() > at NHibernate.Impl.SessionImpl.Execute(IExecutable executable) > at NHibernate.Impl.SessionImpl.ExecuteAll(IList list) > at NHibernate.Impl.SessionImpl.Execute() > Took me the better part of a day to figure out that I had a trigger which was affecting the row count. If the TooManyRowsAffectedException is passed to MessageHelper.InfoString, then we get a message that makes it much easier to determine what is happening. > In NHibernate.Persister.Entity.AbstractEntityPersister.Check(int rows, object id, int tableNumber, IExpectation expectation, IDbCommand statement) > catch (TooManyRowsAffectedException ex) > { > throw new HibernateException( > "Duplicate identifier in table for: " + > MessageHelper.InfoString(this, id, Factory),ex); > } > Now we get a better msg: > NHibernate.HibernateException: Duplicate identifier in table for: [Singletree.Webpdm.Core.Domain.Folder#89193] ---> NHibernate.AdoNet.TooManyRowsAffectedException: Unexpected row count: 2; expected: 1 -- 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 |
|
From: NHibernate J. <mik...@us...> - 2007-01-02 09:30:28
|
[ http://jira.nhibernate.org/browse/NH-842?page=all ] Sergey Koshcheyev updated NH-842: --------------------------------- Fix Version: 1.2.0.Beta3 Priority: Major (was: Critical) > Generated SQL column name aliased wrong? > ---------------------------------------- > > Key: NH-842 > URL: http://jira.nhibernate.org/browse/NH-842 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0.2, 1.0.3 > Reporter: Ka Man Tong > Fix For: 1.2.0.Beta3 > Attachments: Account-orig.hbm.xml, Account.cs, Account.hbm.xml > > I have over 200 fields defined for a table accessing MSSQL 2000. > Some fields have similar prefix (accountId, accountNumber, accountCategoryCode, etc) and I can see NHibernate generate the retrival SQL using the same prefix with some additional numbers and underscore as the column alias. > All fields are in Int32, except one which is of String type. > When retrieving, I got Number Format Exception when NHibernate tries to read some Int32 fields. As I suspect that it was the Nullable issues and I have changed all Int32 fields to NullableInt32. However the case is still the same. > The field mapping XML is defined without any particular order of the fields. > But when I tried to group all AccountXXX fields at the top of the mapping XML, the Number Format Exception doesn't appear anymore. > Is the field mapping ordering important? -- 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 |
35 messages has been excluded from this view by a project administrator.
