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...> - 2006-12-22 03:08:42
|
[ http://jira.nhibernate.org/browse/NH-842?page=all ] Ka Man Tong updated NH-842: --------------------------- Attachment: Account-orig.hbm.xml Original mapping which cause the error. (Visible to jira-users) > 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 > Priority: Critical > 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...> - 2006-12-22 03:04:25
|
[ http://jira.nhibernate.org/browse/NH-842?page=all ] Ka Man Tong updated NH-842: --------------------------- Attachment: Account.hbm.xml Mapping file after re-ordering. (Visible to jira-users) > 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 > Priority: Critical > Attachments: 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...> - 2006-12-22 03:04:24
|
[ http://jira.nhibernate.org/browse/NH-842?page=all ] Ka Man Tong updated NH-842: --------------------------- Attachment: Account.cs Actual POCO class. (Visible to jira-users) > 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 > Priority: Critical > Attachments: 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...> - 2006-12-22 03:01:25
|
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
Priority: Critical
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...> - 2006-12-21 14:03:28
|
[ http://jira.nhibernate.org/browse/NH-841?page=all ] Sergio updated NH-841: ---------------------- Attachment: BUGAccess.rar a little example. > 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 > 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...> - 2006-12-21 11:54:25
|
[ http://jira.nhibernate.org/browse/NH-841?page=comments#action_14650 ] Sergey Koshcheyev commented on NH-841: -------------------------------------- Please attach a minimal test case. > 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 > > 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...> - 2006-12-21 11:50:28
|
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
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...> - 2006-12-21 01:51:27
|
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: LATER, 1.2.0.Beta3
Reporter: Shane Walters
Priority: Minor
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...> - 2006-12-20 19:52:24
|
[ http://jira.nhibernate.org/browse/NH-839?page=all ] John Chapman updated NH-839: ---------------------------- Attachment: PersistentGenericMap.cs Updated PersistentGenericMap which resolves this issue. > 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...> - 2006-12-20 18:54:30
|
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
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...> - 2006-12-20 07:31:29
|
[ http://jira.nhibernate.org/browse/NH-784?page=all ] Sergey Koshcheyev resolved NH-784: ---------------------------------- Fix Version: (was: 1.2.0.Beta3) Resolution: Cannot Reproduce Resolving since no test case supplied. > NHibernate should throw exception on failed driver load > ------------------------------------------------------- > > Key: NH-784 > URL: http://jira.nhibernate.org/browse/NH-784 > Project: NHibernate > Type: Improvement > Components: Data Providers > Versions: 1.2.0.Beta2 > Reporter: Al Twohill > Priority: Trivial > > For full background on where this issue arises from, see http://forum.hibernate.org/viewtopic.php?t=966582&highlight= > When Configuration.Configure() is called, if NHibernate is unable to load a database driver for whatever reason (missing dll, incorrect hibernate.cfg.xml, etc) it falls back to returning a UserSuppliedConnectionProvider without an ADO.Net connection attached to it. This causes any use of Session (eg accessing database) to throw an exception. This is extremely difficult to debug, as there is absolutely no indication as to why a UserSuppliedConnectionProvider is returned. > I propose that instead of returning a UserSuppliedConnectionProvider, NHibernate should throw an exception along the lines of "Cannot Load Driver", and give a reason why. -- 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...> - 2006-12-19 13:11:34
|
[ http://jira.nhibernate.org/browse/NH-32?page=all ] Sergey Koshcheyev updated NH-32: -------------------------------- Comment: was deleted > ByteFX.Data was renamed to ByteFX.MySqlClient > --------------------------------------------- > > Key: NH-32 > URL: http://jira.nhibernate.org/browse/NH-32 > Project: NHibernate > Type: Task > Components: Data Providers > Versions: beta-0.7 > Reporter: Peter Smulovics > Assignee: Mike Doerfler > Priority: Trivial > Fix For: beta-0.7 > Attachments: MySQLDialect.cs.patch, MySql.TestResult.xml, mysql-connector-net-patch.zip > > ByteFX.Data was renamed to ByteFX.MySqlClient by bytefx, so the driver for bytefx should be updated to load the command and connection object from the right dll. > Instead of > connectionType = System.Type.GetType("ByteFX.Data.MySqlClient.MySqlConnection, ByteFX.Data"); > commandType = System.Type.GetType("ByteFX.Data.MySqlClient.MySqlCommand, ByteFX.Data"); > connectionType = System.Type.GetType("ByteFX.Data.MySqlClient.MySqlConnection, ByteFX.MySqlClient"); > commandType = System.Type.GetType("ByteFX.Data.MySqlClient.MySqlCommand, ByteFX.MySqlClient"); > should be written. > As I saw, the internal naming of the namespaces and classes wasn't changed. -- 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...> - 2006-12-18 15:28:36
|
[ http://jira.nhibernate.org/browse/NH-837?page=all ] Sergey Koshcheyev updated NH-837: --------------------------------- Fix Version: 1.2.0.Beta3 Priority: Minor (was: Major) > 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...> - 2006-12-18 15:26:38
|
[ http://jira.nhibernate.org/browse/NH-837?page=comments#action_14626 ] Sergey Koshcheyev commented on NH-837: -------------------------------------- I will implement it like in H3.2.1 then. > 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 > > 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...> - 2006-12-18 15:23:36
|
[ http://jira.nhibernate.org/browse/NH-837?page=comments#action_14625 ] Christophe Vigouroux commented on NH-837: ----------------------------------------- I've just looked to the Hibernate 3.2.1 version of DB2400Dialect and it is implemented like this : public String getLimitString(String sql, int offset, int limit) { return new StringBuffer(sql.length() + 40) .append(sql) .append(" fetch first ") .append(limit) .append(" rows only ") .toString(); } The limit is applied but not the offset. The only way to have something like Row_Number as in DB2 UDB is to create a custom function (UDF) which could have the same behavior, but it should not be used in any public version of NHibernate because it would ask users to install this UDF on their database system. > 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 > > 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...> - 2006-12-18 15:06:35
|
[ http://jira.nhibernate.org/browse/NH-837?page=comments#action_14624 ] Christophe Vigouroux commented on NH-837: ----------------------------------------- Obviously RRN() is not an equivalent to Row_Number. It returns a "relative" row number and cannot be used because it doesn't return the row number of the result set, only the row number of the physical table. I don't know any way to get the row number of the result set, or any other way to ask DB2/400 to fetch the rows starting from an offet... > 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 > > 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...> - 2006-12-18 14:48:36
|
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
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...> - 2006-12-18 14:17:35
|
[ http://jira.nhibernate.org/browse/NH-837?page=comments#action_14623 ] Christophe Vigouroux commented on NH-837: ----------------------------------------- Ok I can try to do this. > 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 > > 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...> - 2006-12-18 14:05:37
|
[ http://jira.nhibernate.org/browse/NH-837?page=comments#action_14622 ] Sergey Koshcheyev commented on NH-837: -------------------------------------- Can you provide the required changes in form of a patch? I don't have access to DB2 so I can't add and test this myself. > 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 > > 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...> - 2006-12-18 14:02:34
|
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
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...> - 2006-12-18 13:47:41
|
[ http://jira.nhibernate.org/browse/NH-714?page=all ] Sergey Koshcheyev updated NH-714: --------------------------------- Comment: was deleted > Persistor Inheritance for Dynamic Proxies > ----------------------------------------- > > Key: NH-714 > URL: http://jira.nhibernate.org/browse/NH-714 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2, 1.0.2 > Reporter: Curtis Schlak > Priority: Minor > Fix For: LATER > Attachments: version-1.x.patches.zip > > I have the opportunity to work with NHibernate in a project at work. We use dynamically-generated proxy objects for use in our application which renders the static NHibernate mapping files useless. We have found that a new feature allowing the framework to search the inheritance hierarchy for persisters used by the proxy's base class allows the transparent use of the dynamically-generated proxy objects. Please find in the attached ZIP archive file two patches that we have used to implement this feature, one patch for the 1.0 release branch and one for the upcoming 1.2 release branch in your development trunk. > USAGE > To activate this feature, add the property "hibernate.inherit_persisters" with a value of "true" to the configuration. > CHANGES > In Version 1.0 Release Branch > * In NHibernate.Test-1.1 project: > - Added the virtual "ExtraProperties" property to the TestCase class. > - Added the virtual "ExtraProperties" property to the TestCase class. > - Added the "Subclass\InheritPersisterFixture.cs" class to test the functionality. > * In NHibernate-1.1 project: > - Changed the "GetPersister(Type)" method in the SessionFactoryImpl class to search for inherited persisters. > In Trunk, along with the changes above, > * In NHibernate.Test-1.1 project: > - Cleaned up the NHibernate.Tests-1.1.csproj to compile. > - Removed the App.config file due to incompatibility with the .NET 1.1 framwork. > - Added the App-1.1.config file for .NET 1.1 Framework compatibility. > - Changed the projects PreBuildEvent to copy the App-1.1.config file. > * In NHibernate-1.1 project: > - Cleaned up the NHibernate-1.1.csproj file to compile. -- 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...> - 2006-12-18 13:47:39
|
[ http://jira.nhibernate.org/browse/NH-528?page=all ] Sergey Koshcheyev updated NH-528: --------------------------------- Comment: was deleted > Fix GROUP BY example in documentation (GROUP BY object instance does not work) > ------------------------------------------------------------------------------ > > Key: NH-528 > URL: http://jira.nhibernate.org/browse/NH-528 > Project: NHibernate > Type: Bug > Components: Documentation > Versions: 1.0.2 > Reporter: Nels P. Olsen > Priority: Minor > Fix For: 1.2.0.Beta2 > > Chapter 11 of the Hibernate documentation shows three HQL examples where GROUP BY is used with an object instance. E.g. > select cat, count( elements(cat.kittens) ) > from eg.Cat cat group by cat > This does not work. Refer to the following forum posts for details: > http://forum.hibernate.org/viewtopic.php?t=953716 > http://forum.hibernate.org/viewtopic.php?t=950514 -- 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...> - 2006-12-15 11:54:33
|
[ http://jira.nhibernate.org/browse/NH-830?page=all ] Sergey Koshcheyev closed NH-830: -------------------------------- Resolution: Fixed > ICriteria does not automatically flush the session for many-to-many association change > -------------------------------------------------------------------------------------- > > Key: NH-830 > URL: http://jira.nhibernate.org/browse/NH-830 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Kailuo Wang > Fix For: 1.2.0.Beta3 > Attachments: SessFlush.zip > > It seems that, unlike IQuery, the ICriteria won't automatically flush the session for many-to-many association changes. > Note that these symptom only happens when the following 2 conditions are satisfied: > 1) the change is about a many-to-many association. It seems work fine with changes to one-to-many assocication > 2) the related entities are just reloaded from the database prior to the query. If the entities are just created and saved, the criteria will flush the session prior the query. > While you can also find the test case in the attachment, here is the code: > //Setup the test data > Cat mum = new Cat(); > Cat son = new Cat(); > sess.Save(mum); > sess.Save(son); > sess.Flush(); > //reload the data and then setup the many-to-many association > mum = sess.Get<Cat>(mum.Id); > son = sess.Get<Cat>(son.Id); > mum.Children.Add(son); > son.Parents.Add(mum); > sess.FlushMode = FlushMode.Auto; > //Use criteria API to search first > IList result = sess.CreateCriteria(typeof (Cat)) > .CreateAlias("Children", "child") > .Add(Expression.Eq("child.Id", son.Id)) > .List(); > //the criteria failed to find the mum cat with the child > Assert.AreEqual(0, result.Count); > > //then use HQL query to search > result = sess.CreateQuery("from Cat c where :son in elements c.Children ") > .SetEntity("son", son) > .List(); > //HQL query automatically flush the sess and thus find the change > Assert.AreEqual(1, result.Count); > //then use the same criteria to search again > result = sess.CreateCriteria(typeof(Cat)) > .CreateAlias("Children", "child") > .Add(Expression.Eq("child.Id", son.Id)) > .List(); > //find the result this time since the session was already flushed by the previous query > Assert.AreEqual(1, result.Count); > <?xml version="1.0" encoding="utf-8" ?> > <hibernate-mapping xmlns="urn:nhibernate-mapping-2.2" schema="dbo" assembly="NHSessTest" default-lazy="false"> > <class name="NHSessTest.Cat" > > <id name="Id" type="Int32" unsaved-value="0" > > <generator class="identity" /> > </id> > <set name="Children" lazy="true" table="ChildrenParents" > > <key column="Parent" /> > <many-to-many class="NHSessTest.Cat" column="Child" /> > </set> > <set name="Parents" lazy="true" inverse="true" table="ChildrenParents" > > <key column="Child" /> > <many-to-many class="NHSessTest.Cat" column="Parent" /> > </set> > </class> > </hibernate-mapping> > namespace NHSessTest > { > public class Cat > { > private int id; > private ISet children = new HashedSet(); > private ISet parents = new HashedSet(); > public int Id > { > get { return id; } > set { id = value; } > } > public ISet Children { > get { return children; } > set { children = value; } > } > public ISet Parents { > get { return parents; } > set { parents = value; } > } > } > } -- 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.
