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-04 09:46:31
|
[ http://jira.nhibernate.org/browse/NH-829?page=all ] Sergey Koshcheyev updated NH-829: --------------------------------- Fix Version: 1.2.0.CR1 > pagination select doesn't support 'distinct' for NHibernate.Dialect.FirebirdDialect > ----------------------------------------------------------------------------------- > > Key: NH-829 > URL: http://jira.nhibernate.org/browse/NH-829 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Edward Zhou > Fix For: 1.2.0.CR1 > > Dialect: NHibernate.Dialect.FirebirdDialect > driver_class: NHibernate.Driver.FirebirdClientDriver > dotNet Framework 2.0 > Firebird 2.0 final > Firebird .Net Provider 2.01 > I encountered an bug, when I put 'distinct' into the HQL statement under pagination, it will cause failure: > eg: > [code] > string hql = "select distinct po from PurchaseBill po left join fetch po.Company company join po.Items pi where (po.BillDate >= :beginDate) and (po.BillDate <= :endDate) and (pi.Product.Id like :productId) order by po.BillDate Desc, po.BillId Desc" > IQuery query = session.CreateQuery(hql); > // seting up parameters > // .. > IList<PurchaseBill> list = query.SetFirstResult(0).SetMaxResults(100).List<PurchaseBill>(); > [/code] > it will gets an error. and I trace the sql generated by NHibernate is: > select distinct first 100 purchasebi0_.f_key_id as f1_16_0_, ... from t_purchase_bill purchasebi0_ left outer join t_company company1_ on purchasebi0_.f_company_id=company1_.f_key_id inner join t_purchase_item items2_ on purchasebi0_.f_key_id=items2_.f_bill_key_id, t_product product3_ where ((product3_.f_id like @p0 and items2_.f_product_id=product3_.f_key_id)) order by purchasebi0_.f_bill_date Desc , purchasebi0_.f_bill_id Desc > Obviously, the keyword 'distinct' is placed in wrong position. it should be placed like > select first 100 distinct ..... -- 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-04 09:35:32
|
pagination select doesn't support 'distinct' for NHibernate.Dialect.FirebirdDialect
-----------------------------------------------------------------------------------
Key: NH-829
URL: http://jira.nhibernate.org/browse/NH-829
Project: NHibernate
Type: Bug
Components: Core
Versions: 1.2.0.Beta2
Reporter: Edward Zhou
Dialect: NHibernate.Dialect.FirebirdDialect
driver_class: NHibernate.Driver.FirebirdClientDriver
dotNet Framework 2.0
Firebird 2.0 final
Firebird .Net Provider 2.01
I encountered an bug, when I put 'distinct' into the HQL statement under pagination, it will cause failure:
eg:
[code]
string hql = "select distinct po from PurchaseBill po left join fetch po.Company company join po.Items pi where (po.BillDate >= :beginDate) and (po.BillDate <= :endDate) and (pi.Product.Id like :productId) order by po.BillDate Desc, po.BillId Desc"
IQuery query = session.CreateQuery(hql);
// seting up parameters
// ..
IList<PurchaseBill> list = query.SetFirstResult(0).SetMaxResults(100).List<PurchaseBill>();
[/code]
it will gets an error. and I trace the sql generated by NHibernate is:
select distinct first 100 purchasebi0_.f_key_id as f1_16_0_, ... from t_purchase_bill purchasebi0_ left outer join t_company company1_ on purchasebi0_.f_company_id=company1_.f_key_id inner join t_purchase_item items2_ on purchasebi0_.f_key_id=items2_.f_bill_key_id, t_product product3_ where ((product3_.f_id like @p0 and items2_.f_product_id=product3_.f_key_id)) order by purchasebi0_.f_bill_date Desc , purchasebi0_.f_bill_id Desc
Obviously, the keyword 'distinct' is placed in wrong position. it should be placed like
select first 100 distinct .....
--
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-04 06:44:34
|
[ http://jira.nhibernate.org/browse/NH-540?page=3Dall ] Sergey Koshcheyev updated NH-540: --------------------------------- Comment: was deleted > Register of AnsiChar type > ------------------------- > > Key: NH-540 > URL: http://jira.nhibernate.org/browse/NH-540 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0.2 > Reporter: Andr=C3=A9 Luiz > Priority: Minor > Fix For: 1.0.3, 1.2.0.Alpha1 > Attachments: TestCase.zip > > I had solicited in NH-493 in the creation of an AnsiChar type that would = permit work with character parameters in a Oracle Database behavior. This t= ype was created in the 1.0.2 but it's register was not made by the TypeFact= ory class of NHibernate. I would like to receive the solution to this issue= as fast as you can because my project it's stopped only waiting this solut= ion to be deployed. --=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-12-04 06:15:37
|
[ http://jira.nhibernate.org/browse/NH-662?page=all ] Sergey Koshcheyev updated NH-662: --------------------------------- Comment: was deleted > Class Hierarchies > ----------------- > > Key: NH-662 > URL: http://jira.nhibernate.org/browse/NH-662 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Anton Gogolev > Priority: Minor > Fix For: LATER > > NH can only persist/load classes explicitly mapped to database tables in HBM files. On the one hand, this is quite logical. But on the other it limits further use of mapped classes. For instance, it is impossible to inherit from them and save the ancestor since its type is not mentioned anywhere in the mapping files. Here's an example: > // Base is mapped to, say, Base table in Base.hbm.xml > class Base > { > public int A > { get ...; set ... } > protected virtual Foo() > { > // Some logic. > } > } > // Derived has no mapping file > class Derived : Base > { > protected override Foo() > { > // Some other logic > } > } > static void Main() > { > ISession session = sessionFactory.OpenSession(); > Base base = new Base(); > base.A = 12; > session.Save(base); // This succeeds > base = session.Load(typeof(Base), 2) as Base; // This succeeds as well > base = new Derived(); // Note "Derived" here > base.A = 13; > session.Save(base); // And this fails > // We won't even get here, but if we did, > // this would have failed too > base = session.Load(typeof(Derived), 3) as Derived; > } > As you can see, the logic behind this is quite OOP-ish :) You inherit from some class to extend its functionality and state (in other words, functions and member variables). However, this is not possible with NHibernate, since it requires every derived class to be mapped somehow. > How I see it done (conceptually) is as follows. > Upon persisting an entity NH should traverse a list of base classes of the entity being persisted, until it finds a type which is mapped to a database table. This type is used to persist an entity. > When loading an entity from the database, NH can freely create an instance of derived class, since it is given its type (typeof(Derived) in the example above). Then again it traveses a list of base classes, and loads derived object as an object of base class. Of course some properties remain uninitialized, but that's not a problem, I think. -- 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-04 06:13:33
|
[ http://jira.nhibernate.org/browse/NH-540?page=3Dall ] Sergey Koshcheyev updated NH-540: --------------------------------- Comment: was deleted > Register of AnsiChar type > ------------------------- > > Key: NH-540 > URL: http://jira.nhibernate.org/browse/NH-540 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0.2 > Reporter: Andr=C3=A9 Luiz > Priority: Minor > Fix For: 1.0.3, 1.2.0.Alpha1 > Attachments: TestCase.zip > > I had solicited in NH-493 in the creation of an AnsiChar type that would = permit work with character parameters in a Oracle Database behavior. This t= ype was created in the 1.0.2 but it's register was not made by the TypeFact= ory class of NHibernate. I would like to receive the solution to this issue= as fast as you can because my project it's stopped only waiting this solut= ion to be deployed. --=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-30 14:51:29
|
[ http://jira.nhibernate.org/browse/NH-370?page=all ] Sergey Koshcheyev resolved NH-370: ---------------------------------- Resolution: Fixed > Add Configuration.SetDefaultAssembly and SetDefaultNamespace methods > -------------------------------------------------------------------- > > 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-30 14:49:31
|
[ http://jira.nhibernate.org/browse/NH-370?page=all ] Sergey Koshcheyev updated NH-370: --------------------------------- Summary: Add Configuration.SetDefaultAssembly and SetDefaultNamespace methods (was: A way to specify the domain assembly) > Add Configuration.SetDefaultAssembly and SetDefaultNamespace methods > -------------------------------------------------------------------- > > 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-30 10:13:32
|
[ http://jira.nhibernate.org/browse/NH-825?page=all ] Ayende Rahien resolved NH-825: ------------------------------ Fix Version: 1.2.0.CR1 Resolution: Fixed Fixed and modified HashtableCache to show same behavior as other caches > QueryKey doesn't take into account the entity ID when generating ToString() > --------------------------------------------------------------------------- > > Key: NH-825 > URL: http://jira.nhibernate.org/browse/NH-825 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Ayende Rahien > Assignee: Ayende Rahien > Priority: Critical > Fix For: 1.2.0.CR1 > > The issue is that when a query in the following form is issued: > emp = (Employee.Id = 1} > from Salary s where s.Employee = emp; > And then stored in the cache, the key for it is something like: > select * from Salaries where s.Employee=?;named parameters={emp=Model.Employee} > Thus, not taking into account the entity id, and returning the wrong result back. -- 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-30 09:05:30
|
Port connection release mode from H3
------------------------------------
Key: NH-828
URL: http://jira.nhibernate.org/browse/NH-828
Project: NHibernate
Type: New Feature
Components: Core
Versions: 1.2.0.Beta2
Reporter: Sergey Koshcheyev
--
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-30 08:39:30
|
[ http://jira.nhibernate.org/browse/NH-666?page=all ] Sergey Koshcheyev closed NH-666: -------------------------------- Resolution: Fixed Changed SetParameterList to take non-generic IEnumerable, so you can pass a generic enumerable to it as well. > 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 |
|
From: NHibernate J. <mik...@us...> - 2006-11-29 13:50:41
|
[ http://jira.nhibernate.org/browse/NH-729?page=comments#action_14502 ] Sergey Koshcheyev commented on NH-729: -------------------------------------- Committed ManagedWebSessionContext. It binds a session to the current HttpContext, and will require the user to write a HttpModule to open/close the session for each request. There is one such module in NHibernate.Example.Web, I don't know if it should be moved to NHibernate itself. > 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-29 13:46:42
|
[ http://jira.nhibernate.org/browse/NH-808?page=all ] Sergey Koshcheyev resolved NH-808: ---------------------------------- Resolution: Fixed > Type of count(*) should be Int64 > -------------------------------- > > Key: NH-808 > URL: http://jira.nhibernate.org/browse/NH-808 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Sergey Koshcheyev > Priority: Trivial > 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-29 12:07:43
|
[ http://jira.nhibernate.org/browse/NH-442?page=all ] Sergey Koshcheyev closed NH-442: -------------------------------- Resolution: Fixed Verified that NH works under medium trust (example is in SVN). The only significant limitation is that DynamicProxy throws a SecurityException so proxies have to be disabled. > Medium Trust level support > -------------------------- > > Key: NH-442 > URL: http://jira.nhibernate.org/browse/NH-442 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.0 > Reporter: Steen Rabol > Fix For: 1.2.0.CR1 > > Security execption is thrown if you use MHibernate on a server with medium trust level eg. web sites hosted on a shrared server. A possbible solution is shown in ASP.Net forum : http://nhibernate.sourceforge.net/forum/viewtopic.php?t=184 -- 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-29 08:02:37
|
Add a way to issue several queries in one round-trip
----------------------------------------------------
Key: NH-827
URL: http://jira.nhibernate.org/browse/NH-827
Project: NHibernate
Type: New Feature
Components: Core
Versions: 1.2.0.Beta2
Reporter: Ayende Rahien
Assigned to: Ayende Rahien
This feature is aimed at being able to issue several (read) queries in a single round-trip.
In SQL it is;
Select * from Employess;
SELECT count(*) From Employess
etc...
NHibernate should have a method like;
IList results = session.ExecuteQueries(getAllEmployeesPaged, getCountOfEmployees);
employees = results[0];
int count = (int)results[1][0];
I think that this is something cross-database, but it has probably different semantics, so it will also need a way for the driver to say it is supported, and a way to merge the queries together.
Maybe also a way to check if this is valid (over 2100 params in SQL Server, for instnace) although the DB will do 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-29 07:57:39
|
[ http://jira.nhibernate.org/browse/NH-826?page=comments#action_14500 ] Aaron Jensen commented on NH-826: --------------------------------- Oops, just realized I accidentally set this as a Blocker priority, sorry about that. It is blocking us from migrating to 1.2, so I'd love to see it fixed sooner than later, but it is hardly a full-on Blocker. > 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 > Priority: Blocker > Attachments: 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...> - 2006-11-29 07:51:39
|
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
Priority: Blocker
Attachments: 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...> - 2006-11-28 22:04:31
|
[ http://jira.nhibernate.org/browse/NH-825?page=comments#action_14493 ] Ayende Rahien commented on NH-825: ---------------------------------- This is on SysCache. Specifically, I am talking about SysCache.GetCacheKey(); private string GetCacheKey( object key ) { return String.Concat( _cacheKeyPrefix, _region, ":", key.ToString(), "@", key.GetHashCode() ); } when we are talking about cached queries the key is a QueryKey, and the problem is that the ToString() of the QueryKey doesn't take into account that the entity class may have not overriden the ToString() method. > QueryKey doesn't take into account the entity ID when generating ToString() > --------------------------------------------------------------------------- > > Key: NH-825 > URL: http://jira.nhibernate.org/browse/NH-825 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Ayende Rahien > Assignee: Ayende Rahien > Priority: Critical > > The issue is that when a query in the following form is issued: > emp = (Employee.Id = 1} > from Salary s where s.Employee = emp; > And then stored in the cache, the key for it is something like: > select * from Salaries where s.Employee=?;named parameters={emp=Model.Employee} > Thus, not taking into account the entity id, and returning the wrong result back. -- 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-28 19:34:32
|
[ http://jira.nhibernate.org/browse/NH-825?page=comments#action_14492 ] Sergey Koshcheyev commented on NH-825: -------------------------------------- Doesn't sound right - caching does not depend on ToString of the key only, as far as I know. Which cache provider are you testing this with? > QueryKey doesn't take into account the entity ID when generating ToString() > --------------------------------------------------------------------------- > > Key: NH-825 > URL: http://jira.nhibernate.org/browse/NH-825 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Ayende Rahien > Assignee: Ayende Rahien > Priority: Critical > > The issue is that when a query in the following form is issued: > emp = (Employee.Id = 1} > from Salary s where s.Employee = emp; > And then stored in the cache, the key for it is something like: > select * from Salaries where s.Employee=?;named parameters={emp=Model.Employee} > Thus, not taking into account the entity id, and returning the wrong result back. -- 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-28 19:11:34
|
QueryKey doesn't take into account the entity ID when generating ToString()
---------------------------------------------------------------------------
Key: NH-825
URL: http://jira.nhibernate.org/browse/NH-825
Project: NHibernate
Type: Bug
Components: Core
Versions: 1.2.0.Beta2
Reporter: Ayende Rahien
Assigned to: Ayende Rahien
Priority: Critical
The issue is that when a query in the following form is issued:
emp = (Employee.Id = 1}
from Salary s where s.Employee = emp;
And then stored in the cache, the key for it is something like:
select * from Salaries where s.Employee=?;named parameters={emp=Model.Employee}
Thus, not taking into account the entity id, and returning the wrong result back.
--
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-28 15:28:38
|
GetClassname cannot parse generic classnames
--------------------------------------------
Key: NH-824
URL: http://jira.nhibernate.org/browse/NH-824
Project: NHibernate
Type: Bug
Components: Core
Versions: 1.2.0.Beta2
Reporter: Michael Abraham
Attachments: GetClassnameBug.zip
There appears to be a bug in NHibernate.Util.StringHelper.GetClassname. The code assumes that the last period in a fully-qualified class name immediately precedes the unqualified class name. That is not true for generic classes. GetClassname gets the unqualified class name of the type parameter with ']' appended. I believe that the same issue may affect StringHelper.Unqualify when it is applied to class names, but I don't know when (or whether) that ever happens. The attached VS2005 solution illustrates the problem.
--
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-28 13:12:36
|
[ http://jira.nhibernate.org/browse/NH-467?page=all ] Christian Bauer updated NH-467: ------------------------------- Comment: was deleted > Many-to-one ignores "WHERE" class mapping element on associated Class > --------------------------------------------------------------------- > > Key: NH-467 > URL: http://jira.nhibernate.org/browse/NH-467 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0 > Reporter: Alexei > Fix For: 1.2.0.Alpha1 > > For example a Employee->User association > Class Employee: > <class name="Employee, MyApp" table="Employee" where="inactive=0" > > ... > <many-to-one name="User" class="User, MyApp" > column="UserId" unique="true" not-null="false" > > Class User: > <class name="User, MyApp" table="Users" where="inactive=0" > > Will generate SQL: > SELECT... FROM Employee this LEFT OUTER JOIN Users user1_ ON this.UserId=user1_.id WHERE this.inactive=0 > The User objects will be retrived ignoring the "inactive" flag on Users table. Similar behaviour with <bag>, <one-to-one> and others. -- 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-28 13:12:35
|
[ http://jira.nhibernate.org/browse/NH-528?page=all ] Christian Bauer 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 |
35 messages has been excluded from this view by a project administrator.
