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-13 19:45:17
|
[ http://jira.nhibernate.org/browse/NH-370?page=all ] Sergey Koshcheyev updated NH-370: --------------------------------- Fix Version: LATER Version: 1.2.0.Beta2 > 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: LATER > > 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-13 19:42:31
|
[ http://jira.nhibernate.org/browse/NH-429?page=all ] Sergey Koshcheyev updated NH-429: --------------------------------- Fix Version: LATER > Lazy load columns > ----------------- > > Key: NH-429 > URL: http://jira.nhibernate.org/browse/NH-429 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.0 > Reporter: Xianfeng Lu > Fix For: LATER > > NPersist allows you to lazy load any property you like - for example a very big text property (Employee.LifeStory) that you don't want to load from the database every time you load an employee. > Furthermore, any unloaded property automatically becomes lazy loading. This means that if you issue an NPath statement like the following: > Select Id, FirstName from Employee Where ID = 42 > Then the LastName property, which wasn't loaded by the query, will automatically become lazy loading and be loaded with data the first time you access it (if you access it). > I hope NHibernate will have column lazy loading feature ASAP. -- 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-13 19:39:02
|
[ http://jira.nhibernate.org/browse/NH-442?page=all ] Sergey Koshcheyev updated NH-442: --------------------------------- Fix Version: 1.2.0.CR1 > 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-13 19:32:43
|
[ http://jira.nhibernate.org/browse/NH-800?page=all ] Sergey Koshcheyev updated NH-800: --------------------------------- Fix Version: 1.2.0.CR1 > Switch to SandCastle to generate the API documentation > ------------------------------------------------------ > > Key: NH-800 > URL: http://jira.nhibernate.org/browse/NH-800 > Project: NHibernate > Type: Task > Components: Core > Versions: 1.2.0.Beta1 > Reporter: Sergey Koshcheyev > Fix For: 1.2.0.CR1 > > NDoc doesn't work with generics, there is a problem generating VS.NET 2003 documentation, and it is also dead. -- 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-13 19:30:13
|
[ http://jira.nhibernate.org/browse/NH-379?page=all ] Sergey Koshcheyev closed NH-379: -------------------------------- Resolution: Duplicate Will be fixed by NH-628. > Support for standard concatenating operator in HQL > -------------------------------------------------- > > Key: NH-379 > URL: http://jira.nhibernate.org/browse/NH-379 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.0 > Reporter: Andrey Bezugliy > > Currently HQL does not provide standard way for string concatenation. It would be great to have that way because there is no way to specify concatentation operator that would allow use the same HQL statement for MS SQL and Oracle. > I think that it would be essential to add a property to IDialect and support the concatenation function or operation in HQL. -- 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-13 19:22:43
|
[ http://jira.nhibernate.org/browse/NH-662?page=all ] Sergey Koshcheyev updated NH-662: --------------------------------- Fix Version: LATER Version: 1.2.0.Beta2 > 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-11-13 19:21:26
|
[ http://jira.nhibernate.org/browse/NH-788?page=all ] Sergey Koshcheyev closed NH-788: -------------------------------- Resolution: Incomplete > Incrementing a nullable <Version> field fails > --------------------------------------------- > > Key: NH-788 > URL: http://jira.nhibernate.org/browse/NH-788 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.Beta1 > Reporter: Jens Dein > Priority: Minor > Attachments: Serialno.hbm.xml > > I have defined my version tag like this : > <version > name="Hbversion" > column="HBVersion" > type="System.Int32" > unsaved-value="null" > /> > and in my class like this : > private System.Int32? _hbversion; > and when trying to persist the code I get an error in the following code : > public class Int32Type : ValueTypeType, IDiscriminatorType, IVersionType > public virtual object Next( object current ) > { > return ( ( int )current ) + 1; > } > besause current is typecasted to int without checking for null. Code might be changed to the following : > public virtual object Next( object current ) > { > if (current == null) > return Seed; > else > return ((int)current) + 1; > } > I hope I havent misunderstood totally how to use these nullables, but I believe I found advise on the net stating that it should be possible to do it this way in the 1.2 version. > Using .NET 2.0 of course and SQL Server 2005. -- 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-13 19:20:17
|
[ http://jira.nhibernate.org/browse/NH-298?page=all ] Sergey Koshcheyev updated NH-298: --------------------------------- Fix Version: LATER Component: Core Version: 1.2.0.Beta2 > After, deleting an item which belongs to a <list> the list indices are not modified > ----------------------------------------------------------------------------------- > > Key: NH-298 > URL: http://jira.nhibernate.org/browse/NH-298 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2, beta-0.7 > Environment: WindowsXP > Reporter: Scott Buzan > Fix For: LATER > > Posted: Fri May 27, 2005 5:02 pm Post subject: updating <list> index values when removing children > -------------------------------------------------------------------------------- > I posted this message to the sourceforge forum...a request was made that I create a JIRA issue. > I'm using a <list> for one end of a many-to-many association. When I remove an item from the collection the indices are not updated in the database? For example if index 2 is removed, the database will show indices: 0,1,3,4,5,...etc. > Parent class mapping: > Code: > <list name="ConceptGroups" table="Application_ConceptGroup" cascade="save-update" lazy="true"> > <key column="ApplicationPK"/> > <index column="Position"/> > <many-to-many class="Units.ConceptGroup, Test" column="ConceptGroupPK"></many-to-many> > </list> > Child class mapping: > Code: > <bag name="Applications" table="Application_ConceptGroup" cascade="save-update" lazy="true"> > <key column="ConceptGroupPK"/> > <many-to-many class="Application, Test" column="ApplicationPK"></many-to-many> > </bag> > originally both classes were mapped using a <bag>; however, I have to maintain the order of the list for one end of the association...so I changed the parent class to use the <list>. Everything else seems to work 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-13 19:20:08
|
[ http://jira.nhibernate.org/browse/NH-707?page=all ] Sergey Koshcheyev updated NH-707: --------------------------------- Fix Version: LATER > External exception handling in the Factory > ------------------------------------------ > > Key: NH-707 > URL: http://jira.nhibernate.org/browse/NH-707 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Alpha1 > Reporter: Alexei > Fix For: LATER > Attachments: Changes.doc, IExceptionHandler.cs > > Make possible external exception handling in nHibernate so internal exeptions could be handeled. For example - exeptions coming from Proxy/LazyInitializer.cs. > Ideally, nHibernate should expose IExceptionHander that external applications should implement in order to pass in an exception object to nHibernate -- 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-13 19:14:57
|
[ http://jira.nhibernate.org/browse/NH-424?page=all ] Sergey Koshcheyev updated NH-424: --------------------------------- Fix Version: LATER > Add [ Table per subclass, using a discriminator ] Support to Nhibernate > ----------------------------------------------------------------------- > > Key: NH-424 > URL: http://jira.nhibernate.org/browse/NH-424 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.0.1 > Reporter: Knight > Fix For: LATER > > Add "Table per subclass, using a discriminator" support to Nhibernate. > Now that Nhibernate has reached a stable release it would be nice to see such feature from > Hibernate 3 ported. -- 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-13 19:12:10
|
[ http://jira.nhibernate.org/browse/NH-343?page=all ] Sergey Koshcheyev closed NH-343: -------------------------------- Resolution: Won't Fix > Invalid database query generated for mappings with multiple references to a single column > ----------------------------------------------------------------------------------------- > > Key: NH-343 > URL: http://jira.nhibernate.org/browse/NH-343 > Project: NHibernate > Type: Improvement > Components: Core > Versions: beta-0.9 > Environment: SQL Server 2000 > Reporter: Orr Bernstein > Priority: Minor > > When a column appears multiple times in a mapping file, it's included in queries multiple times, yielding database errors. Example: > class A: > ... > <many-to-one name="X"> > <column name="a"/> > <column name="b"/> > </many-to-one> > <many-to-one name="Y"> > <column name="a"/> > <column name="c"/> > </many-to-one> > ... > class B: > <composite-id> > <key-property name="a"/> > <key-property name="z"/> > </composite-id> > ... > With SQL Server 2000, the error reported is: > NHibernate.ADOException: could not synchronize database state with session ---> > System.Data.SqlClient.SqlException: Column name 'XXXXXXX' appears more than once in the result column list. > Statement(s) could not be prepared. > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) > at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() > at NHibernate.Impl.BatcherImpl.ExecuteNonQuery(IDbCommand cmd) > at NHibernate.Impl.NonBatchingBatcher.AddToBatch(Int32 expectedRowCount) > at NHibernate.Persister.EntityPersister.Update(Object id, Object[] fields, Boolean[] includeProperty, Object oldVersion, Object obj, SqlString sqlUpdateString, ISessionImplementor session) > at NHibernate.Persister.EntityPersister.Update(Object id, Object[] fields, Int32[] dirtyFields, Object[] oldFields, Object oldVersion, Object obj, ISessionImplementor session) > at NHibernate.Impl.ScheduledUpdate.Execute() > at NHibernate.Impl.SessionImpl.ExecuteAll(IList list) > at NHibernate.Impl.SessionImpl.Execute() > --- End of inner exception stack trace --- > at NHibernate.Impl.SessionImpl.Execute() > at NHibernate.Impl.SessionImpl.Flush() > at NHibernate.Transaction.AdoTransaction.Commit() > at <application code> > (query is like: > UPDATE Table SET Column1=a, Column2=x, Column3=b, Column2=x, Column4=c WHERE PrimaryKey=d) > One possible solution is to allow this type of mapping, though an extra check done at the time that the query is produced, reducing the query above to include each column only once and throwing an exception if any of the separately provided values for that column are different than the others. One more constraint should be added as well - where the column is furthermore used as part or the whole of the primary key, a check should be done to ensure that none of the foreign-key uses of that column attempt to modify the value to something other than the value of that column in its primary key context. Finally, for sanity's sake, any primary key column should be removed from any modifying reference in the query (i.e. set pk_col1=...), which because of above-mentioned check wouldn't leave out any excepted changes to the row. > Or at very least, we oughta fix the "distinctColumns" bug for better error handling. I think it's a one-liner for beta-0.9 - insert at line 217 of Persister.EntityParser: > distinctColumns.AddAll( propertyColumnNames ); -- 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-13 19:09:45
|
[ http://jira.nhibernate.org/browse/NH-743?page=all ] Sergey Koshcheyev updated NH-743: --------------------------------- Fix Version: 1.2.0.CR1 > change BatcherImpl to public > ---------------------------- > > Key: NH-743 > URL: http://jira.nhibernate.org/browse/NH-743 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta1 > Reporter: legowo budianto > Priority: Trivial > Fix For: 1.2.0.CR1 > > After review, testing and being amazed the SqlBatchingBatcher with the use of SqlCommandSet. I notice that the similiar pattern can be used to Oracle Database using the lattest ODP through associative array parameter. > I make some POC but being blocked by the attribute of the abstract class BatcherImpl, since it being marked as internal. > Suggestion is to mark it as public so third party can make their own batcher implementation outside nhibernate as core. -- 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-13 19:08:39
|
[ http://jira.nhibernate.org/browse/NH-616?page=all ] Sergey Koshcheyev updated NH-616: --------------------------------- Fix Version: LATER > Entry-Level Task List > --------------------- > > Key: NH-616 > URL: http://jira.nhibernate.org/browse/NH-616 > Project: NHibernate > Type: Task > Components: Core > Reporter: Sergey Koshcheyev > Priority: Trivial > Fix For: LATER > > This issue contains links to NHibernate tasks somebody could work on who wants to contribute code to NHibernate but is not yet familiar with its internals. This means that either the task is downright easy, or it requires some work, but I have thought it out and have a clear idea of how to implement it, so I can provide guidance. > The main requirement for any submitted patches is that the code should follow Hibernate 3.x if it has a similar feature, unless there is a strong enough reason for doing things in a different way. > In general, fixing bugs or doing something platform-specific is a strong reason, while just implementing a feature differently because you could not be bothered to look at the Hibernate code is not. -- 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-13 19:04:56
|
[ http://jira.nhibernate.org/browse/NH-419?page=all ] Sergey Koshcheyev updated NH-419: --------------------------------- Fix Version: (was: LATER) 1.2.0.CR1 > Adding relation name when throwing a cascade error > -------------------------------------------------- > > Key: NH-419 > URL: http://jira.nhibernate.org/browse/NH-419 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.0.1 > Reporter: Ayende Rahien > Fix For: 1.2.0.CR1 > > I recently go the following exception: > NHibernate.ObjectDeletedException : deleted object would be re-saved by cascade (remove deleted object from associations): 18, of class: Model.Assignment > As you can see, it doesn't say what is the relation that is causing this. I had to resort to debugging NHibernate in order to find out (there were several, actually). > It would be much easier if we could get the relation that is causing 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-13 19:04:37
|
[ http://jira.nhibernate.org/browse/NH-797?page=all ] Sergey Koshcheyev closed NH-797: -------------------------------- Resolution: Not an Issue Not a problem, transactions are definitely supposed to be rolled back in Dispose. > IDbTransaction doesn't get rolled back automatically in AdoTransaction.Dispose > ------------------------------------------------------------------------------ > > Key: NH-797 > URL: http://jira.nhibernate.org/browse/NH-797 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.0.3, 1.2.0.Beta1 > Reporter: Sergey Koshcheyev > Priority: Trivial > -- 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-13 18:56:07
|
[ http://jira.nhibernate.org/browse/NH-543?page=all ] Sergey Koshcheyev updated NH-543: --------------------------------- Fix Version: LATER Version: 1.2.0.Beta2 > Adding GetEntityName to IInterceptor (H3.0 feature) > --------------------------------------------------- > > Key: NH-543 > URL: http://jira.nhibernate.org/browse/NH-543 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Ernst Naezer > Priority: Trivial > Fix For: LATER > Attachments: GetEntityInterceptor.patch, GetEntityPostloadInterceptor.patch, GetEntityPostloadInterceptor.patch, NHibernate.patch > > Hibernate 3.x has an GetEnityName function in the interceptor that is used by the factory to get the Persistory before saving the object. > This allows the user to create proxy objects and directly pass them to NH. > More information can be found here: http://www.hibernate.org/339.html > Attached is a patch that adds this functionality. I haven't made an test cases yet. -- 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-13 18:56:06
|
[ http://jira.nhibernate.org/browse/NH-285?page=all ] Sergey Koshcheyev updated NH-285: --------------------------------- Fix Version: LATER Version: 1.2.0.Beta2 > Allow nested classes in HQL > --------------------------- > > Key: NH-285 > URL: http://jira.nhibernate.org/browse/NH-285 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2, beta-0.8.3 > Environment: windows 2003,.net 1.1 > Reporter: Ma Liang > Fix For: LATER > > If I want to query a nested class using ISession.Find, how could I make my from expression? > Using "from parentclass+nestedclass" will cause NHibernate to throw a exception. -- 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-13 18:52:55
|
[ http://jira.nhibernate.org/browse/NH-461?page=all ] Sergey Koshcheyev closed NH-461: -------------------------------- Resolution: Won't Fix Won't fix it now that SQL Server 2005 has satisfactory support for paging. > Slow paging in sql server > ------------------------- > > Key: NH-461 > URL: http://jira.nhibernate.org/browse/NH-461 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.0 > Reporter: Ron Liu > > For example, I have 5000 records in a table. When I retrives the first 100 rows, the speed is ok, but it getting slower and slower when I try to retrives the next and next 100 rows. I monitored the sql server, the generated sql is like "select top 100" for the 1st, but "select top 200" for the 2nd, ... > I think it can be improved by created a temp table or a table varible which just store all the ids at first, and then render back by join that temp table. -- 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-13 18:44:21
|
[ http://jira.nhibernate.org/browse/NH-517?page=all ] Sergey Koshcheyev updated NH-517: --------------------------------- Fix Version: LATER > Unnecessary selects when mapped as class instead of column > ---------------------------------------------------------- > > Key: NH-517 > URL: http://jira.nhibernate.org/browse/NH-517 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.0.1 > Reporter: Ruurd Boeke > Fix For: LATER > Attachments: NH517.rar > > I've delved deeper into the problem described by: http://jira.nhibernate.org/browse/NH-435 > It seems I have the same kind of problem, but it has nothing to do with using an outer select. > Short summary: I'm getting N selects when I have mapped a one-to-many relation, and in the many-side, the composite-ID maps towards the 'one' with a key-many-to-one instead of a key-property. > This means that nHibernate is using one well-constructed query to get all the info it needs, and then sends a SELECT for every row it got back like this: select parentID from parents where parentID = :parentid > In my current situation, this leads to several thousands of selects. -- 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-13 18:44:18
|
[ http://jira.nhibernate.org/browse/NH-419?page=all ] Sergey Koshcheyev updated NH-419: --------------------------------- Fix Version: LATER > Adding relation name when throwing a cascade error > -------------------------------------------------- > > Key: NH-419 > URL: http://jira.nhibernate.org/browse/NH-419 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.0.1 > Reporter: Ayende Rahien > Fix For: 1.2.0.CR1 > > I recently go the following exception: > NHibernate.ObjectDeletedException : deleted object would be re-saved by cascade (remove deleted object from associations): 18, of class: Model.Assignment > As you can see, it doesn't say what is the relation that is causing this. I had to resort to debugging NHibernate in order to find out (there were several, actually). > It would be much easier if we could get the relation that is causing 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-13 18:43:48
|
[ http://jira.nhibernate.org/browse/NH-766?page=all ] Sergey Koshcheyev updated NH-766: --------------------------------- Comment: was deleted > Avoid joins on <composite-key><key-many-to-one> queries > ------------------------------------------------------- > > Key: NH-766 > URL: http://jira.nhibernate.org/browse/NH-766 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.0.2 > Reporter: Kirk Wylie > Priority: Trivial > Fix For: LATER > > This is being promoted from something I posted on the NHibernate forums. > Using NHibernate 1.0.2.0 against Oracle 9. > I'm working with an existing schema which isn't using surrogate keys, and I have a composite key of the form: > <class name="CalculatedRating" ...> > <composite-id> > <key-property name="EffectiveDate" column="EFFECTIVE_DATE"/> > <key-many-to-one name="FdeOrganization" column="ORGANIZATION_ID" .../> > </composite-id> > ... > </class> > Using this query: > from CalculatedRating cr > inner join fetch cr.FdeOrganization fdeOrg > left join fetch fdeOrg.Attributes as attribute > inner join fetch attribute.AttributeType > where cr.EffectiveDate = > (select max(cr2.EffectiveDate) > from CalculatedRating cr2 > where cr2.EffectiveDate >= :EffectiveDate) > order by cr.FdeOrganization.OrgId > NHibernate is quite correctly generating the SQL necessary to completely manifest the CalculatedRating element in a single query. However, after executing that query, it then still proceeds to do the N+1 select on FdeOrganization. > As in this application I'm actually using quite a few cases where I'm successfully using the inner join fetch technique against FdeOrganization, I can only assume that this is a problem related to key-many-to-one rather than many-to-one. > After further investigation, I can establish that Hibernate 3.1.3 exposes the exact same functionality. I'm filing this first against NHibernate since that's where I first discovered it, however, since it affects Hibernate as well it might be better filed against that, and I can do so if needed. -- 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-13 18:40:12
|
[ http://jira.nhibernate.org/browse/NH-786?page=all ] Sergey Koshcheyev updated NH-786: --------------------------------- Fix Version: LATER Version: 1.2.0.Beta2 > Port statistics from H3 > ----------------------- > > Key: NH-786 > URL: http://jira.nhibernate.org/browse/NH-786 > Project: NHibernate > Type: New Feature > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Sergey Koshcheyev > Priority: Trivial > Fix For: LATER > -- 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-13 18:38:54
|
[ http://jira.nhibernate.org/browse/NH-647?page=all ] Sergey Koshcheyev closed NH-647: -------------------------------- Resolution: Fixed Fixed awhile ago when better SQL queries were introduced. > Bugs in CreateSQLQuery > ---------------------- > > Key: NH-647 > URL: http://jira.nhibernate.org/browse/NH-647 > Project: NHibernate > Type: Improvement > Components: Core > Reporter: David Cederbaum > Priority: Minor > > I am experiencing the same problem as this posting: > http://forum.hibernate.org/viewtopic.php?p=2277750&sid=2c988f4fe0a5f7f179f873a84b1b7167 > This is really a showstopper for me as I want to be able to execute arbitrary native SQL queries and bring back selected columns only, not all columns. The bug reported above looks like NHibernate expects all columns be brought back. > Could you let me know when this may be fixed? -- 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-13 18:38:43
|
[ http://jira.nhibernate.org/browse/NH-784?page=all ] Sergey Koshcheyev updated NH-784: --------------------------------- Fix Version: 1.2.0.CR1 Version: 1.2.0.Beta2 > 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 > Fix For: 1.2.0.CR1 > > 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-11-13 18:37:34
|
[ http://jira.nhibernate.org/browse/NH-754?page=all ] Sergey Koshcheyev updated NH-754: --------------------------------- Fix Version: LATER > Implement support for .net 2.0 System.Transactions.TransactionScope > ------------------------------------------------------------------- > > Key: NH-754 > URL: http://jira.nhibernate.org/browse/NH-754 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta1 > Reporter: Michael Teper > Priority: Critical > Fix For: LATER > > Right now NH 1.2 does not appear capable of participating in .net 2 TransactionScope transactions. Not sure what the fix entails, but adding this support would be really really nice, particularly in light of vista's transactioning file system 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 |
35 messages has been excluded from this view by a project administrator.
