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-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
|
|
From: NHibernate J. <mik...@us...> - 2006-11-24 10:05:28
|
[ http://jira.nhibernate.org/browse/NH-370?page=comments#action_14480 ] Sergey Koshcheyev commented on NH-370: -------------------------------------- Added SetDefaultAssembly and SetDefaultNamespace to Configuration to solve part of this problem. > A way to specify the domain assembly > ------------------------------------ > > Key: NH-370 > URL: http://jira.nhibernate.org/browse/NH-370 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Sergey Koshcheyev > Fix For: 1.2.0.CR1 > > This is just an idea. Adding a method to Configuration to specify the domain objects assembly could make other features of NHibernate easier to use. Classes will not need to be imported to be used from HQL ("select new" or enum constants), mapping files will not need the assembly attribute since its value could be automatically taken from the assembly name. > Instead of a method, a parameter could be passed to Configuration, like cfg = new Configuration("My.Assembly.Name") (with an overload taking System.Reflection.Assembly). -- 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-11-24 10:03:34
|
[ http://jira.nhibernate.org/browse/NH-370?page=all ] Sergey Koshcheyev updated NH-370: --------------------------------- Fix Version: (was: LATER) 1.2.0.CR1 > A way to specify the domain assembly > ------------------------------------ > > Key: NH-370 > URL: http://jira.nhibernate.org/browse/NH-370 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Sergey Koshcheyev > Fix For: 1.2.0.CR1 > > This is just an idea. Adding a method to Configuration to specify the domain objects assembly could make other features of NHibernate easier to use. Classes will not need to be imported to be used from HQL ("select new" or enum constants), mapping files will not need the assembly attribute since its value could be automatically taken from the assembly name. > Instead of a method, a parameter could be passed to Configuration, like cfg = new Configuration("My.Assembly.Name") (with an overload taking System.Reflection.Assembly). -- 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-11-22 11:23:23
|
[ http://jira.nhibernate.org/browse/NH-729?page=comments#action_14472 ] Sergey Koshcheyev commented on NH-729: -------------------------------------- No, only the framework is done. In other words, only the skeleton is implemented, this task is about adding meat to it. > Add ICurrentSessionContext implementation for ASP.NET apps. > ----------------------------------------------------------- > > Key: NH-729 > URL: http://jira.nhibernate.org/browse/NH-729 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta1 > Reporter: Sergey Koshcheyev > Priority: Minor > Fix For: 1.2.0.CR1 > -- 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-11-22 11:20:25
|
[ http://jira.nhibernate.org/browse/NH-729?page=comments#action_14471 ] Ayende Rahien commented on NH-729: ---------------------------------- Isn't this already implmented? > Add ICurrentSessionContext implementation for ASP.NET apps. > ----------------------------------------------------------- > > Key: NH-729 > URL: http://jira.nhibernate.org/browse/NH-729 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta1 > Reporter: Sergey Koshcheyev > Priority: Minor > Fix For: 1.2.0.CR1 > -- 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-11-22 11:18:24
|
[ http://jira.nhibernate.org/browse/NH-819?page=all ] Ayende Rahien resolved NH-819: ------------------------------ Resolution: Fixed Updated to memcachedclient 1.1.14 > Memcached.Client library is using log4net 1.2.9, instead of 1.2.10 > ------------------------------------------------------------------ > > Key: NH-819 > URL: http://jira.nhibernate.org/browse/NH-819 > Project: NHibernate > Type: Bug > Components: Contrib > Versions: 1.2.0.Beta2 > Reporter: Ayende Rahien > Assignee: Ayende Rahien > Fix For: 1.2.0.CR1 > > This disable the use of MemCached caching with NH 1.2 > Temporary solution may be to compile Memcached client ourself, but we lose the strong name that way. > I am going to contact the developers and see if they can push a version with 1.2.10, and then move to that. -- 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-11-21 13:59:41
|
[ http://jira.nhibernate.org/browse/NH-822?page=all ] Ayende Rahien resolved NH-822: ------------------------------ Resolution: Fixed fixed in svn > Can't use MemCached for query cache because of big key size. > ------------------------------------------------------------ > > Key: NH-822 > URL: http://jira.nhibernate.org/browse/NH-822 > Project: NHibernate > Type: Bug > Components: Contrib > Versions: 1.2.0.Beta2 > Reporter: Ayende Rahien > Assignee: Ayende Rahien > > Mem Cache keys are limited to 250 characters, but a lot of queries are a lot bigger than that. > This usually means that we need to hash the key itself. > Probably MD5 would be the best solution, with check to see if the key size if beyond 250 (to reduce perf of hashing). -- 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-11-21 13:59:40
|
[ http://jira.nhibernate.org/browse/NH-813?page=all ] Ayende Rahien resolved NH-813: ------------------------------ Resolution: Fixed fixed in svn > CacheKey key is invalid - memcached fails to store objects. > ----------------------------------------------------------- > > Key: NH-813 > URL: http://jira.nhibernate.org/browse/NH-813 > Project: NHibernate > Type: Patch > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Stuart Carnie > Assignee: Ayende Rahien > Fix For: 1.2.0.CR1 > Attachments: cachekey-fix.patch > > The CacheKey derives from IdentifierSpace, which is EntityMetaModel.RootTypeAssemblyQualifiedName. This name contains spaces, which causes an issue with MemCache, in the 'set' command. With the spaces in the key, an invalid command is sent to the memcached server. > I have provided a patch that exposes a new property on EntityMetaModel, RootName (to match the property name in Hibernate), which simply replaces the spaces with underscores '_'. Now memcached caching works fine. -- 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-11-21 12:29:38
|
Can't use MemCached for query cache because of big key size.
------------------------------------------------------------
Key: NH-822
URL: http://jira.nhibernate.org/browse/NH-822
Project: NHibernate
Type: Bug
Components: Contrib
Versions: 1.2.0.Beta2
Reporter: Ayende Rahien
Assigned to: Ayende Rahien
Mem Cache keys are limited to 250 characters, but a lot of queries are a lot bigger than that.
This usually means that we need to hash the key itself.
Probably MD5 would be the best solution, with check to see if the key size if beyond 250 (to reduce perf of hashing).
--
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-11-21 09:38:36
|
[ http://jira.nhibernate.org/browse/NH-813?page=all ] Ayende Rahien reassigned NH-813: -------------------------------- Assign To: Ayende Rahien > CacheKey key is invalid - memcached fails to store objects. > ----------------------------------------------------------- > > Key: NH-813 > URL: http://jira.nhibernate.org/browse/NH-813 > Project: NHibernate > Type: Patch > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Stuart Carnie > Assignee: Ayende Rahien > Fix For: 1.2.0.CR1 > Attachments: cachekey-fix.patch > > The CacheKey derives from IdentifierSpace, which is EntityMetaModel.RootTypeAssemblyQualifiedName. This name contains spaces, which causes an issue with MemCache, in the 'set' command. With the spaces in the key, an invalid command is sent to the memcached server. > I have provided a patch that exposes a new property on EntityMetaModel, RootName (to match the property name in Hibernate), which simply replaces the spaces with underscores '_'. Now memcached caching works fine. -- 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-11-21 08:57:42
|
[ http://jira.nhibernate.org/browse/NH-779?page=all ] Sergey Koshcheyev updated NH-779: --------------------------------- Comment: was deleted > abstract class not recognized using multiple mapping files > ---------------------------------------------------------- > > Key: NH-779 > URL: http://jira.nhibernate.org/browse/NH-779 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0.2 > Reporter: Hace > Attachments: JoinedSubClass.zip > > When an abstract class and (one or more) joined-subclasses are not in one mapping file, but joined-subclasses are in separate mappingfiles, the connection between the abstract class and the joined subclasses is lost. An error of 'cannot instantiate abstract class' occurs. > [ AbstractClass.hbm.xml ] > <hibernate-mapping> > <class name="Namespace.Common.AbstractClass, Namespace.Common" table="GeneralItem"> > <id name="GeneralItemId" type="Int32" column="GeneralItemId" > > <generator class="identity"/> > </id> > <property name="GeneralText" column="GeneralText" /> > > <joined-subclass name="Namespace.Common.A.ConcreteClassA, Namespace.Common.A" table="ItemsA" extends="Namespace.Common.AbstractClass, Namespace.Common"> > <key column="GeneralItemId" /> > ..concrete properties for A.. > </joined-subclass> > > </class> > </hibernate-mapping> > [ ConcreteClassB.hbm.xml ] > <hibernate-mapping> > <joined-subclass name="Namespace.Common.B.ConcreteClassB, Namespace.Common.B" table="ItemsB" extends="Namespace.Common.AbstractClass, Namespace.Common"> > <key column="GeneralItemId" /> > ..concrete properties for B.. > </joined-subclass> > </hibernate-mapping> > Items for ConcreteClassB will not be loaded correctly, only because the joined-subclass is not in the SAME mappingfile as ConcreteClassA ? > [ Code ] > List<AbstractClass> itemList = new List<AbstractClass>(); > ISession session = OurSession.CurrentSession; > ICriteria NHibernateCriteria = session.CreateCriteria(typeof(AbstractClass)); > NHibernateCriteria.Add(Expression.In("GeneralItemId", generalItemIds.ToArray())); > try > { > IEnumerable<AbstractClass> enumerable = (AbstractClass[])ArrayList.Adapter(NHibernateCriteria.List()).ToArray(typeof(AbstractClass)); > itemList = new List<AbstractClass>(enumerable); > } > catch(Exception exception) > { > ... log exception.. > } > ...... > dostuff > foreach(ConcreteClassA in itemList) > .... > [ /code ] -- 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-11-21 08:57:40
|
[ http://jira.nhibernate.org/browse/NH-804?page=all ] Sergey Koshcheyev updated NH-804: --------------------------------- Comment: was deleted > Implement the SUBSELECT FETCH and BATCH FETCH > --------------------------------------------- > > Key: NH-804 > URL: http://jira.nhibernate.org/browse/NH-804 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Franz Meier > Fix For: LATER > > like in hibernate 3.x > sess.CreateQuery("from Book b SUBSELECT FETCH b.publisher") > sess.CreateQuery("from Book b BATCH FETCH SIZE=5 b.publisher") > the strange thing is, that you can configure it in the mapping xml file, > but you cannot use it in the CreateQuery -- 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-11-21 08:57:38
|
[ http://jira.nhibernate.org/browse/NH-774?page=all ] Sergey Koshcheyev updated NH-774: --------------------------------- Comment: was deleted > Oracle Performance using Load > ----------------------------- > > Key: NH-774 > URL: http://jira.nhibernate.org/browse/NH-774 > Project: NHibernate > Type: Patch > Components: Data Providers > Versions: 1.0, 1.0.2 > Reporter: Jorge > Attachments: CreateQuery.txt, CreateSQLQuery.txt, Load.txt, Load.txt, PerformanceNHibernate.rar, PerformanceNHibernate.rar > > I have developed a application using NHibernate version 1.0.2.0 (in the version 1.0.0.0 the same behaviour) over ORACLE version 10.2.0.1.0 in the Server and the same version for the Oracle Client. > I am using C#, .NET 2.0 and Visual Studio 2005. > I have a table with more than 1 million records, and the object to build has one property for each field in the table. It means nothing special. > When i am trying to load one object using the primary key with session.Load() spends about 3 seconds, while if i use session.CreateSQLQuery() to get the same object using the primary key as weel it spends about 0,05 seconds. the query using CreateSQLQuery is: > SELECT {a.*} FROM REGDI a WHERE REGDIID='" + myREGDIID + "'"; > and query in the Load is : > SELECT regdi0_.REGDIID as REGDIID0_, regdi0_.REGID as REGID0_, regdi0_.DITAHUN as DITAHUN0_, regdi0_.DIKODE as DIKODE0_, regdi0_.DINOMOR as DINOMOR0_, regdi0_.DITANGGAL as DITANGGAL0_ FROM REGDI regdi0_ WHERE regdi0_.REGDIID=:p0 > If do the same test with a few data in the table (about 10,000) is working both methods quickly. But if the table has 1 million records the load take a long time. > I have debud the application and the problem is in the method DoQuery() in the class NHibernate.Loader.Loader. And in the line 326: > for( count = 0; count < maxRows && rs.Read(); count++ ) > To do the rs.Read() takes about 3 seconds. > the object rs is a System.Data.OracleClient.OracleDataReader > and the query to do is : > SELECT regdi0_.REGDIID as REGDIID0_, regdi0_.REGID as REGID0_, > regdi0_.DITAHUN as DITAHUN0_, regdi0_.DIKODE as DIKODE0_, > regdi0_.DINOMOR as DINOMOR0_, regdi0_.DITANGGAL as DITANGGAL0_ > FROM REGDI regdi0_ WHERE regdi0_.REGDIID=:p0 > I think there is something strange building the OracleCommand inside the NHibernate. Someone else has the same problem?? Anyone has some clues? > I attach a small project in VS2005 showing the problem. > Thank you in advance. > Jorge. > ********* XML Mapping ***** > <?xml version="1.0" encoding="utf-8" ?> > <hibernate-mapping xmlns="urn:nhibernate-mapping-2.0"> > <class name="PerformanceNHibernate.RegDI, PerformanceNHibernate" > table="REGDI" > > <id name="RDI_RegDIId" column="REGDIID" type="String"> > <generator class="uuid.hex"/> > </id> > <property name ="RDI_RegisterLink" column ="REGID" type ="String"/> > <property column="DIKODE" type="String" name="RDI_DICode" not-null="true" length="6" /> > <property column="DINOMOR" type="String" name="RDI_DINomor" length="30" /> > <property column="DITAHUN" type="Int32" name="RDI_DIYear" /> > <property column="DITANGGAL" type="DateTime" name="RDI_DIDate" /> > </class> > </hibernate-mapping> > ******* Class Definition ******** > using System; > namespace PerformanceNHibernate > { > [Serializable] > public class RegDI > { > private string _regdiid;//identifier > private string _regid; > private string _dicode; > private string _dinomor; > private int? _diyear; > private DateTime? _didate; > public RegDI() > { > } > public string RDI_RegDIId > { > get { return _regdiid; } > set { _regdiid = value; } > } > public string RDI_RegisterLink > { > get { return _regid; } > set { _regid = value; } > } > /// <summary> > /// > /// </summary> public string RDI_DICode > { > get { return _dicode; } > set { _dicode = value; } > } > /// <summary> > /// > /// </summary> public string RDI_DINomor > { > get { return _dinomor; } > set { _dinomor = value; } > } > /// <summary> > /// > /// </summary> public int? RDI_DIYear > { > get { return _diyear; } > set { _diyear = value; } > } > /// <summary> > /// > /// </summary> public DateTime? RDI_DIDate > { > get { return _didate; } > set { _didate = value; } > } > public override bool Equals(object obj) > { > bool response = false; > if (this.RDI_RegDIId.Equals(((RegDI)obj).RDI_RegDIId)) > { > response = true; > } > return response; > } > public override int GetHashCode() > { > return ((String)this.RDI_RegDIId).GetHashCode(); > } > }//end of public class > }//end of namespace > ******* Table in ORACLE ************ > CREATE TABLE REGDI ( > REGDIID VARCHAR2(32) NOT NULL, > REGID VARCHAR2(32) NOT NULL, > DIKODE VARCHAR2(6) NOT NULL, > DINOMOR VARCHAR2(30), > DITAHUN NUMBER(4), > DITANGGAL DATE); > ALTER TABLE REGDI ADD ( > CONSTRAINT PK_REGDI PRIMARY KEY (REGDIID)); > CREATE INDEX I1TRANSDI ON REGDI (DIKODE, DINOMOR, DITAHUN); > CREATE INDEX I2TRANSDI ON REGDI (DIKODE, DITAHUN, DINOMOR); > CREATE INDEX I2REGDI ON REGDI (REGID, DIKODE); > ***************************** -- 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-11-21 08:57:37
|
[ http://jira.nhibernate.org/browse/NH-769?page=all ] Sergey Koshcheyev updated NH-769: --------------------------------- Comment: was deleted > Improve serialization of Session > -------------------------------- > > Key: NH-769 > URL: http://jira.nhibernate.org/browse/NH-769 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Peter Smulovics > Priority: Minor > Fix For: LATER > > Serialization of Session object is done using the default methods, resulting in time and space consuming binary objects. Technologies like FastSerializer ( http://www.codeproject.com/dotnet/FastSerializer.asp ) may help a lot. -- 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-11-21 08:57:37
|
[ http://jira.nhibernate.org/browse/NH-765?page=all ] Sergey Koshcheyev updated NH-765: --------------------------------- Comment: was deleted > Use "(" and ")" to enclose the ToString of LogicalExpression.cs > --------------------------------------------------------------- > > Key: NH-765 > URL: http://jira.nhibernate.org/browse/NH-765 > Project: NHibernate > Type: Patch > Components: Core > Versions: 1.2.0.Beta1 > Reporter: Kailuo Wang > Priority: Trivial > Fix For: 1.2.0.Beta2 > Attachments: LogicExpressionToString.patch > > - return _lhs.ToString() + ' ' + Op + ' ' + _rhs.ToString(); > + return "(" + _lhs.ToString() + ' ' + Op + ' ' + _rhs.ToString() + ")"; -- 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-11-21 08:55:44
|
[ http://jira.nhibernate.org/browse/NH-761?page=all ] Sergey Koshcheyev updated NH-761: --------------------------------- Comment: was deleted > Change ISession.Get() to initialize a proxy if it returns one, like in H3.2 > --------------------------------------------------------------------------- > > Key: NH-761 > URL: http://jira.nhibernate.org/browse/NH-761 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta1 > Reporter: Sergey Koshcheyev > Priority: Trivial > Fix For: 1.2.0.Beta2 > -- 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-11-21 08:55:39
|
[ http://jira.nhibernate.org/browse/NH-815?page=all ] Sergey Koshcheyev updated NH-815: --------------------------------- Comment: was deleted > SQLQueryImpl fails to bind parameter lists > ------------------------------------------ > > Key: NH-815 > URL: http://jira.nhibernate.org/browse/NH-815 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Peter Jaffe > Fix For: 1.2.0.CR1 > > The SQLQueryImpl class does not bind parameter lists properly. This is very easy to reproduce with a simple SQLQuery that has a single named parameter in the WHERE clause (e.g. "where id in (:idList)") and then use the ISQLQuery.SetParameterList("idList", someCollection). This works with an IQuery but fails with an ISQLQuery. > I debugged through the source of the 1.2.0 Beta2 and the fix appears very straightforward. See the code snippet below that indicates where the method argument "parameters" should probably be used instead of the class's NamedParams property. > public class SqlQueryImpl : AbstractQueryImpl, ISQLQuery > { > ... > public NativeSQLQuerySpecification GenerateQuerySpecification(IDictionary parameters) > { > return new NativeSQLQuerySpecification( > BindParameterLists(NamedParams), <-- ** Probably should have been "parameters" ** > GetQueryReturns(), > querySpaces); > } > ... > } > I'm using the MS SQL Server ADO.NET provider and running under .NET 2.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...> - 2006-11-21 08:55:38
|
[ http://jira.nhibernate.org/browse/NH-819?page=all ] Sergey Koshcheyev updated NH-819: --------------------------------- Comment: was deleted > Memcached.Client library is using log4net 1.2.9, instead of 1.2.10 > ------------------------------------------------------------------ > > Key: NH-819 > URL: http://jira.nhibernate.org/browse/NH-819 > Project: NHibernate > Type: Bug > Components: Contrib > Versions: 1.2.0.Beta2 > Reporter: Ayende Rahien > Assignee: Ayende Rahien > Fix For: 1.2.0.CR1 > > This disable the use of MemCached caching with NH 1.2 > Temporary solution may be to compile Memcached client ourself, but we lose the strong name that way. > I am going to contact the developers and see if they can push a version with 1.2.10, and then move to that. -- 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-11-21 08:20:58
|
[ http://jira.nhibernate.org/browse/NH-466?page=comments#action_14451 ] Sergey Koshcheyev commented on NH-466: -------------------------------------- If you had a patch, we could discuss it. > Add <join> mapping element to map one class to several tables > ------------------------------------------------------------- > > Key: NH-466 > URL: http://jira.nhibernate.org/browse/NH-466 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Alexei > Fix For: LATER > > It would be nice to be able to map properties of one class to several tables as Hibernate 3.0 does with a <join> element. > An important feature when working with legacy data models shared by existing applications. -- 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-11-21 08:08:43
|
[ http://jira.nhibernate.org/browse/NH-466?page=3Dcomments#action_1445= 0 ] =20 Taavi K=C3=B5osaar commented on NH-466: ---------------------------------- How would nhibernate developers feel about taking this into nhibernate 1.2 = release ? (although i think new features are not to be added anymore ??) This would be a very valuable addition and a long waited addition. And to sum things up, great work with the API !!! Love to use it !! > Add <join> mapping element to map one class to several tables > ------------------------------------------------------------- > > Key: NH-466 > URL: http://jira.nhibernate.org/browse/NH-466 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Alexei > Fix For: LATER > > It would be nice to be able to map properties of one class to several tab= les as Hibernate 3.0 does with a <join> element. > An important feature when working with legacy data models shared by exist= ing applications. --=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...> - 2006-11-20 17:49:34
|
[ http://jira.nhibernate.org/browse/NH-821?page=comments#action_14448 ] Ayende Rahien commented on NH-821: ---------------------------------- The amount of complexity this feature would bring is very high. In general, this is possible today using the List(IList) overload, and a custom IList implementation, which will call back to your code. The NH Session is currently not re-enterant, and it would take quite an effort to make it so, for little benefit. You correctly identified that proxy evaluation is going to be difficult, this is solvable by issuing the correct query to load the items that you want with projection, with no proxies involved. In general, there is little point in showing the user large amount of data, since they can't grasp it all. Paging / filtering are usually better options. > Streaming ResultSet support > --------------------------- > > Key: NH-821 > URL: http://jira.nhibernate.org/browse/NH-821 > Project: NHibernate > Type: New Feature > Components: Core > Reporter: Jerry Haltom > Priority: Trivial > > NHibernate should provide support for streaming results. A set of methods such as IQuery.List<T>(ListCb<T> cb, int pageSize) could be introduced to support this. The basic idea is that it would result in NH going to the database layer and invoking the callback periodically as it reads and hydrates instances from the underlying databaes connection. This would not be asynchronous. > The major use case for this is in populating a large list view with results as they arrive from the database, when the database supports streaming result sets. The UI could issue a query along with a callback to be invoked when data arrives. As the callback is invokved, the UI would add the data to it's display. This would result in my faster responding interfaces. > This requires a NH Session to be reentrant. Unsure if this is the case currently. The callback will receive instances which the callback may directly manipulate. If it receives an instance which is a proxy, and it attempts to access a property of it which is lazy, it would result in NH intercepting it and reentering it's own code to issue the query for the lazy properties. > No async support would be attempted. The callback would be invokved by NH directly on the thread which originally entered NH. It would be up to the programmer of the callback. > The end result of this is that the UI can start filling in results as the database works to retrieve those results, which might be the case for very long queries. -- 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-11-20 17:29:28
|
Streaming ResultSet support
---------------------------
Key: NH-821
URL: http://jira.nhibernate.org/browse/NH-821
Project: NHibernate
Type: New Feature
Components: Core
Reporter: Jerry Haltom
Priority: Trivial
NHibernate should provide support for streaming results. A set of methods such as IQuery.List<T>(ListCb<T> cb, int pageSize) could be introduced to support this. The basic idea is that it would result in NH going to the database layer and invoking the callback periodically as it reads and hydrates instances from the underlying databaes connection. This would not be asynchronous.
The major use case for this is in populating a large list view with results as they arrive from the database, when the database supports streaming result sets. The UI could issue a query along with a callback to be invoked when data arrives. As the callback is invokved, the UI would add the data to it's display. This would result in my faster responding interfaces.
This requires a NH Session to be reentrant. Unsure if this is the case currently. The callback will receive instances which the callback may directly manipulate. If it receives an instance which is a proxy, and it attempts to access a property of it which is lazy, it would result in NH intercepting it and reentering it's own code to issue the query for the lazy properties.
No async support would be attempted. The callback would be invokved by NH directly on the thread which originally entered NH. It would be up to the programmer of the callback.
The end result of this is that the UI can start filling in results as the database works to retrieve those results, which might be the case for very long queries.
--
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-11-20 16:31:39
|
[ http://jira.nhibernate.org/browse/NH-813?page=comments#action_14447 ] Ayende Rahien commented on NH-813: ---------------------------------- I don't think that the string is going to cause any significant issues, and I don't think that we should change NH to fit the cache. I just run into the same issue today, so that was happy timing > CacheKey key is invalid - memcached fails to store objects. > ----------------------------------------------------------- > > Key: NH-813 > URL: http://jira.nhibernate.org/browse/NH-813 > Project: NHibernate > Type: Patch > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Stuart Carnie > Fix For: 1.2.0.CR1 > Attachments: cachekey-fix.patch > > The CacheKey derives from IdentifierSpace, which is EntityMetaModel.RootTypeAssemblyQualifiedName. This name contains spaces, which causes an issue with MemCache, in the 'set' command. With the spaces in the key, an invalid command is sent to the memcached server. > I have provided a patch that exposes a new property on EntityMetaModel, RootName (to match the property name in Hibernate), which simply replaces the spaces with underscores '_'. Now memcached caching works fine. -- 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-11-20 16:09:36
|
[ http://jira.nhibernate.org/browse/NH-813?page=comments#action_14446 ] Stuart Carnie commented on NH-813: ---------------------------------- I just thought it would be better to format the key appropriately earlier on, for performance reasons. If we do it where I suggested, we only remove the spaces once, when the meta-data for the entity is loaded, rather than every time we need to search for an entity in the cache. This results in less memory pressure, since we're not forced to allocate memory for the new string. Cheers, Stu > CacheKey key is invalid - memcached fails to store objects. > ----------------------------------------------------------- > > Key: NH-813 > URL: http://jira.nhibernate.org/browse/NH-813 > Project: NHibernate > Type: Patch > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Stuart Carnie > Fix For: 1.2.0.CR1 > Attachments: cachekey-fix.patch > > The CacheKey derives from IdentifierSpace, which is EntityMetaModel.RootTypeAssemblyQualifiedName. This name contains spaces, which causes an issue with MemCache, in the 'set' command. With the spaces in the key, an invalid command is sent to the memcached server. > I have provided a patch that exposes a new property on EntityMetaModel, RootName (to match the property name in Hibernate), which simply replaces the spaces with underscores '_'. Now memcached caching works fine. -- 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-11-20 15:32:35
|
[ http://jira.nhibernate.org/browse/NH-666?page=comments#action_14445 ] Sergey Koshcheyev commented on NH-666: -------------------------------------- It does need to be ICollection at least because NHibernate will ask for its Count. > IQuery.SetParameterList should support generics > ----------------------------------------------- > > Key: NH-666 > URL: http://jira.nhibernate.org/browse/NH-666 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Alpha1 > Reporter: Jerry Haltom > Priority: Trivial > Fix For: 1.2.0.CR1 > > IQuery.SetParameterList should support generic collections. I might also name it SetParameters(IEnumerable<>), as it doesn't actually need to set a List, just an enumerable source of values. -- 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.
