nhibernate-issues — Updates to JIRA issues are sent to this list

[nhibernate-issues] [JIRA] Resolved: (NH-752) Informix Dialect

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-752?page=all ]
     
Sergey Koshcheyev resolved NH-752:
----------------------------------

    Resolution: Fixed

> Informix Dialect
> ----------------
>
>          Key: NH-752
>          URL: http://jira.nhibernate.org/browse/NH-752
>      Project: NHibernate
>         Type: New Feature
>   Components: Data Providers
>     Versions: 1.2.0.Beta2
>     Reporter: Robert Sosnowski
>     Priority: Minor
>      Fix For: 1.2.0.CR1
>  Attachments: InformixDialect.zip
>
> I've made Informix dialect. I've tested it on 1.0.2 with Odbc driver (I haven't used native Informix driver because I had some problems with it).
> Dialect for 1.2.0 untested but it should work. The only difference is IdentitySelectString property in 1.0.2 changed to GetIdentitySelectString method in 1.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

[nhibernate-issues] [JIRA] Closed: (NH-743) change BatcherImpl to public

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-743?page=all ]
     
Sergey Koshcheyev closed NH-743:
--------------------------------

    Resolution: Fixed

> 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

[nhibernate-issues] [JIRA] Closed: (NH-811) Automaticall set parent properties on cascading saves

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-811?page=all ]
     
Sergey Koshcheyev closed NH-811:
--------------------------------

    Resolution: Won't Fix

This won't be done because it's not how NHibernate is supposed to work. NHibernate tries to be completely transparent so it won't change properties of your objects by itself.

> Automaticall set parent properties on cascading saves
> -----------------------------------------------------
>
>          Key: NH-811
>          URL: http://jira.nhibernate.org/browse/NH-811
>      Project: NHibernate
>         Type: New Feature
>     Versions: 1.2.0.Beta2
>     Reporter: Tobias Grimm
>     Priority: Trivial

>
> It would be nice, if during a cascading save the parent properties of the list items automatically get set to their parent:
> // Assuming e.g. a one-to-many mapping with cascading save
> class Parent
> {
>     ...
>     public IList<Child> Childs
>     {
>        get { return _childs; }
>        set { _childs = value; }
>     }
> }
> class Child
> {
>     ...
>     public Parent Parent
>     {
>        get { return _parent; }
>        set { _parent = value; }
>     }
> }
> Parent parent = new Parent();
> Child child = new Child();
> // child.Parent should be automatically set by NHibernate,
> // just like parent.Id and child.Id are set as well
> session.Save(parent);
> Assert.AreEqual(parent, child.Parent);

-- 
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

[nhibernate-issues] [JIRA] Created: (NH-811) Automaticall set parent properties on cascading saves

[NHibernate J. <mik...@us...>]

Automaticall set parent properties on cascading saves
-----------------------------------------------------

         Key: NH-811
         URL: http://jira.nhibernate.org/browse/NH-811
     Project: NHibernate
        Type: New Feature
    Versions: 1.2.0.Beta2    
    Reporter: Tobias Grimm
    Priority: Trivial


It would be nice, if during a cascading save the parent properties of the list items automatically get set to their parent:

// Assuming e.g. a one-to-many mapping with cascading save

class Parent
{
    ...
    public IList<Child> Childs
    {
       get { return _childs; }
       set { _childs = value; }
    }
}

class Child
{
    ...
    public Parent Parent
    {
       get { return _parent; }
       set { _parent = value; }
    }
}

Parent parent = new Parent();
Child child = new Child();

// child.Parent should be automatically set by NHibernate,
// just like parent.Id and child.Id are set as well
session.Save(parent);

Assert.AreEqual(parent, child.Parent);


-- 
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

[nhibernate-issues] [JIRA] Closed: (NH-419) Adding relation name when throwing a cascade error

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-419?page=all ]
     
Sergey Koshcheyev closed NH-419:
--------------------------------

    Fix Version:     (was: 1.2.0.CR1)
     Resolution: Won't Fix

Can't do that because the information about the source of cascade is not available at the point where the exception is thrown.

> 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

>
> 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

[nhibernate-issues] [JIRA] Updated: (NH-793) NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-793?page=all ]

Sergey Koshcheyev updated NH-793:
---------------------------------

    Fix Version: 1.2.0.CR1
       Priority: Trivial  (was: Critical)

Ok, I'll fix it in 1.2.0.CR1 then since from your description it looks like it is not critical at all.

> NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".
> -----------------------------------------------------------------------------------------------------------------------
>
>          Key: NH-793
>          URL: http://jira.nhibernate.org/browse/NH-793
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.0.3
>     Reporter: dstefanov
>     Priority: Trivial
>      Fix For: 1.2.0.CR1

>
> public bool Read()
> {
> 	// DS 6/30/06 - If the result is 0 records the read will always return false 
> 	// and the _isMidstream should be false so we don't attempt to read from the 
> 	// reader when we do ReadIntoMemory. We were getting an error 
> 	// "Invalid attempt to read when no data is present" when trying to get data 
> 	// from the reader is such cases.
> 	//
> 	//_isMidstream = true;
> 	//return _reader.Read();
> 	//
> 	_isMidstream = _reader.Read();
> 	return _isMidstream;
> }

-- 
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

[nhibernate-issues] [JIRA] Reopened: (NH-793) NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-793?page=all ]
     
Sergey Koshcheyev reopened NH-793:
----------------------------------


> NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".
> -----------------------------------------------------------------------------------------------------------------------
>
>          Key: NH-793
>          URL: http://jira.nhibernate.org/browse/NH-793
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.0.3
>     Reporter: dstefanov
>     Priority: Critical

>
> public bool Read()
> {
> 	// DS 6/30/06 - If the result is 0 records the read will always return false 
> 	// and the _isMidstream should be false so we don't attempt to read from the 
> 	// reader when we do ReadIntoMemory. We were getting an error 
> 	// "Invalid attempt to read when no data is present" when trying to get data 
> 	// from the reader is such cases.
> 	//
> 	//_isMidstream = true;
> 	//return _reader.Read();
> 	//
> 	_isMidstream = _reader.Read();
> 	return _isMidstream;
> }

-- 
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

[nhibernate-issues] [JIRA] Commented: (NH-793) NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-793?page=comments#action_14402 ]
     
dstefanov commented on NH-793:
------------------------------

( I should correct my previous comment. )

I'm not very familiar with the whole NHibernate API. I'm only using NHybridDataReader and NDataReader in my application.


The fix I'm proposing has been tested and is very easy to check.

As seen from the repro if you Read() from the reader and the result set is empty then the Read() method returns false. In that case the _isMidstream should show if we are in the middle of reading the result set. In this specific case the dataset is empty and should not be considered in the midstream. If the ReadIntoMemory() is called at this moment it checks the _isMidstream and if true assumes it can safely read the record values from the stream - GetValues(). In our case the code fails with exception since the dataset is empty and there is no record to read. The fix sets the _isMidstream to false for this case so the ReadIntoMemory() will call Read() from the reader before it reads the values and the Read() will return false and won't fail. Bottom line is - we can't be in the middle of an empty dataset. 


> NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".
> -----------------------------------------------------------------------------------------------------------------------
>
>          Key: NH-793
>          URL: http://jira.nhibernate.org/browse/NH-793
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.0.3
>     Reporter: dstefanov
>     Priority: Critical

>
> public bool Read()
> {
> 	// DS 6/30/06 - If the result is 0 records the read will always return false 
> 	// and the _isMidstream should be false so we don't attempt to read from the 
> 	// reader when we do ReadIntoMemory. We were getting an error 
> 	// "Invalid attempt to read when no data is present" when trying to get data 
> 	// from the reader is such cases.
> 	//
> 	//_isMidstream = true;
> 	//return _reader.Read();
> 	//
> 	_isMidstream = _reader.Read();
> 	return _isMidstream;
> }

-- 
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

[nhibernate-issues] [JIRA] Commented: (NH-793) NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-793?page=comments#action_14401 ]
     
dstefanov commented on NH-793:
------------------------------

I'm not very familiar with the whole NHibernate API. I'm only using NHybridDataReader and NDataReader in my application.

The fix I'm proposing has been tested and is very easy to check.

As seen from the repro if you Read() from the reader and the result set is empty then the Read() method returns false. In that case the _isMidstream should show if we are in the middle of reading the result set. In this specific case the dataset is empty and should not be considered in the midstream. If the ReadIntoMemory() is called at this moment it checks the _isMidstream and if true assumes it can safely Read() from the stream (and it will get true or false; both valid). In our case the code fails with exception since we are already at the end of the dataset and there is no more data to read. The fix sets the _isMidstream to false for this case so the ReadIntoMemory() won't Read() from the reader and won't fail. Bottom line is - we can't be in the middle of an empty dataset.


> NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".
> -----------------------------------------------------------------------------------------------------------------------
>
>          Key: NH-793
>          URL: http://jira.nhibernate.org/browse/NH-793
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.0.3
>     Reporter: dstefanov
>     Priority: Critical

>
> public bool Read()
> {
> 	// DS 6/30/06 - If the result is 0 records the read will always return false 
> 	// and the _isMidstream should be false so we don't attempt to read from the 
> 	// reader when we do ReadIntoMemory. We were getting an error 
> 	// "Invalid attempt to read when no data is present" when trying to get data 
> 	// from the reader is such cases.
> 	//
> 	//_isMidstream = true;
> 	//return _reader.Read();
> 	//
> 	_isMidstream = _reader.Read();
> 	return _isMidstream;
> }

-- 
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

[nhibernate-issues] [JIRA] Commented: (NH-793) NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-793?page=comments#action_14400 ]
     
Sergey Koshcheyev commented on NH-793:
--------------------------------------

Can you reproduce the bug without using NHybridDataReader directly, i.e. only using public NHibernate API?

> NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".
> -----------------------------------------------------------------------------------------------------------------------
>
>          Key: NH-793
>          URL: http://jira.nhibernate.org/browse/NH-793
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.0.3
>     Reporter: dstefanov
>     Priority: Critical

>
> public bool Read()
> {
> 	// DS 6/30/06 - If the result is 0 records the read will always return false 
> 	// and the _isMidstream should be false so we don't attempt to read from the 
> 	// reader when we do ReadIntoMemory. We were getting an error 
> 	// "Invalid attempt to read when no data is present" when trying to get data 
> 	// from the reader is such cases.
> 	//
> 	//_isMidstream = true;
> 	//return _reader.Read();
> 	//
> 	_isMidstream = _reader.Read();
> 	return _isMidstream;
> }

-- 
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

[nhibernate-issues] [JIRA] Commented: (NH-793) NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-793?page=comments#action_14399 ]
     
dstefanov commented on NH-793:
------------------------------

// to reproduce the bug use this code:

try
{
	string strConn = "Data Source=.;Initial catalog=Northwind;Persist Security Info=False;Integrated Security=SSPI;Connect Timeout=30";
	SqlConnection conn = new SqlConnection( strConn );
	conn.Open();

	SqlCommand cmd = conn.CreateCommand();
	cmd.CommandText = "SELECT * FROM ORDERS WHERE OrderID is null";
        // the result set has no rows (0 rows)

	NHybridDataReader reader = new NHybridDataReader( cmd.ExecuteReader() );
	reader.Read();
	reader.ReadIntoMemory();
}
catch ( Exception ex )
{
	Debug.WriteLine(ex);
}


> NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".
> -----------------------------------------------------------------------------------------------------------------------
>
>          Key: NH-793
>          URL: http://jira.nhibernate.org/browse/NH-793
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.0.3
>     Reporter: dstefanov
>     Priority: Critical

>
> public bool Read()
> {
> 	// DS 6/30/06 - If the result is 0 records the read will always return false 
> 	// and the _isMidstream should be false so we don't attempt to read from the 
> 	// reader when we do ReadIntoMemory. We were getting an error 
> 	// "Invalid attempt to read when no data is present" when trying to get data 
> 	// from the reader is such cases.
> 	//
> 	//_isMidstream = true;
> 	//return _reader.Read();
> 	//
> 	_isMidstream = _reader.Read();
> 	return _isMidstream;
> }

-- 
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

[nhibernate-issues] [JIRA] Commented: (NH-808) Type of count(*) should be Int64

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-808?page=comments#action_14398 ]
     
Fabio Maulo commented on NH-808:
--------------------------------

I don't understand..
		protected class CountQueryFunctionInfo : StandardSQLFunction
		{
			public CountQueryFunctionInfo() : base("count") { }
			public override IType ReturnType(IType columnType, IMapping mapping)
			{
				return NHibernateUtil.Int64;
			}
		}
It is Int64.
There is a different implementation (porting from H3.2) if a dialect use ClassicCountFunction (return type is Int32) but, until now no dialect use it.

Perhaps you mean count in projection criteria. I think is better if the expression ask the IType, of a specific function, to the dialect to don't have different behaviour between Query and Criteria.

> 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

[nhibernate-issues] [JIRA] Closed: (NH-807) Criteria Tests

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-807?page=all ]
     
Sergey Koshcheyev closed NH-807:
--------------------------------

    Resolution: Fixed

> Criteria Tests
> --------------
>
>          Key: NH-807
>          URL: http://jira.nhibernate.org/browse/NH-807
>      Project: NHibernate
>         Type: Patch
>   Components: Tests, Core
>     Versions: 1.2.0.Beta2
>     Reporter: Fabio Maulo
>      Fix For: 1.2.0.CR1
>  Attachments: CriteriaTestAndSomePatch.patch
>
> The patch include:
> - new directory src\NHibernate.Test\Criteria with the port of hibernate-3.2\test\org\hibernate\test\criteria\CriteriaQueryTest.java
> - added [Serializable] of some existing class (for same class adjusted identation)
> - add Expression.IdEq and it's implementation NHibernate/Expression/IdentifierEqExpression.cs
> - in ICriteria add of overload CreateCriteria(string associationPath, JoinType joinType)
> - CriteriaImpl for [Serializable], identation and AddOrder of subcriteria
> - added NHibernate/Property/ChainedPropertyAccessor.cs and changed AliasToBeanResultTransformer to auto-chose access to property or fields
> -PassThroughResultTransformer for [Serializable] and identation

-- 
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

[nhibernate-issues] [JIRA] Updated: (NH-810) Prevent use of many-to-one association in Expression.Eq

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-810?page=all ]

Sergey Koshcheyev updated NH-810:
---------------------------------

    Fix Version: 1.2.0.CR1
      Component: Core
       Priority: Minor  (was: Blocker)
        Summary: Prevent use of many-to-one association in Expression.Eq  (was: many-to-one mapping and Expression.Eq)
           type: Improvement  (was: Bug)

Now that I have looked at it closer, this is expected. You have a type mismatch since you are comparing a User object to its identifier. I'll see whether it is possible to detect this in criteria and throw an appropriate error.

> Prevent use of many-to-one association in Expression.Eq
> -------------------------------------------------------
>
>          Key: NH-810
>          URL: http://jira.nhibernate.org/browse/NH-810
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Beta2
>     Reporter: Sergiy Strelbitskyy
>     Priority: Minor
>      Fix For: 1.2.0.CR1
>  Attachments: IssueDemo.RAR
>
> many-to-one mapping and Expression.Eq fails when trying to do Criteria.List()
> Sample project to reproduce this error in attach.
> Configuration: .NET2, MS SQL 2005
> See also: http://forum.hibernate.org/viewtopic.php?t=967213

-- 
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

[nhibernate-issues] [JIRA] Created: (NH-810) many-to-one mapping and Expression.Eq

[NHibernate J. <mik...@us...>]

many-to-one mapping and Expression.Eq
-------------------------------------

         Key: NH-810
         URL: http://jira.nhibernate.org/browse/NH-810
     Project: NHibernate
        Type: Bug
    Versions: 1.2.0.Beta2    
    Reporter: Sergiy Strelbitskyy
    Priority: Blocker
 Attachments: IssueDemo.RAR

many-to-one mapping and Expression.Eq fails when trying to do Criteria.List()

Sample project to reproduce this error in attach.

Configuration: .NET2, MS SQL 2005

See also: http://forum.hibernate.org/viewtopic.php?t=967213

-- 
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

[nhibernate-issues] [JIRA] Commented: (NH-788) Incrementing a nullable <Version> field fails

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-788?page=comments#action_14391 ]
     
Jens Dein commented on NH-788:
------------------------------

Sorry about that!

I was actually just trying to generate a test case but not w I can't make it fail. I'm a bit new at this so I'm not quite sure what it is I have done - but it seems that the problem is gone.

> 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

[nhibernate-issues] [JIRA] Commented: (NH-784) NHibernate should throw exception on failed driver load

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-784?page=comments#action_14381 ]
     
Al Twohill commented on NH-784:
-------------------------------

One of the problems as I see it is that there are too many possible causes of this problem:

-incorrect value in DriverConnectionProvider field (ie spelling error)
-unknown property in session-factory section
-missing database driver
-missing supporting dlls

These can all trigger this issue, and require different resolutions to be made.
Because of this I beleive that an exception should always be thrown unless a successful connection is able to be made (be it user supplied or NHb configured).


> 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

[nhibernate-issues] [JIRA] Updated: (NH-322) case when...then...else...end in select clause

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-322?page=all ]

Sergey Koshcheyev updated NH-322:
---------------------------------

    Fix Version: LATER
        Version: 1.2.0.Beta2
      Assign To:     (was: Mike Doerfler)

> case when...then...else...end  in select clause
> -----------------------------------------------
>
>          Key: NH-322
>          URL: http://jira.nhibernate.org/browse/NH-322
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Versions: 1.2.0.Beta2
>     Reporter: quixotry
>      Fix For: LATER

>
> currently "case when...then...else...end" is not supported in the select clause. This feature is very useful in some cases.
> Please see HHH-467 for hibernate for more detail.
> Thanks

-- 
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

[nhibernate-issues] [JIRA] Updated: (NH-428) Support Multiple Collections join fetch

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-428?page=all ]

Sergey Koshcheyev updated NH-428:
---------------------------------

    Fix Version: LATER

> Support Multiple Collections join fetch
> ---------------------------------------
>
>          Key: NH-428
>          URL: http://jira.nhibernate.org/browse/NH-428
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Versions: 1.0
>     Reporter: Phoebus Orient
>      Fix For: LATER

>
> There is no issue tracked in this system about this topic. I'd like to add this one.
> Hope supporting multiple collections can be ported from hibernate soon. The related topics about it from forum are here:
> http://nhibernate.sourceforge.net/forum/viewtopic.php?t=952
> http://nhibernate.sourceforge.net/forum/viewtopic.php?t=697

-- 
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

[nhibernate-issues] [JIRA] Updated: (NH-568) year(), month(), date() and some other functions: not supported in HQL

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-568?page=3Dall ]

Sergey Koshcheyev updated NH-568:
---------------------------------

    Fix Version: LATER

> year(), month(),date() and some other functions: not supported in HQL
> ---------------------------------------------------------------------
>
>          Key: NH-568
>          URL: http://jira.nhibernate.org/browse/NH-568
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Ezequiel P=C3=A9rez
>     Priority: Minor
>      Fix For: LATER
>  Attachments: MsSql2000Dialect.cs
>
> Year(), Month() and Day() functions are not supported, at least for MS SQ=
L Server 2000. To use them uncomment lines from 108 to 134 in NHibernate/Di=
alect/MsSql2000Dialect.cs, depending on the functions you need.

--=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

[nhibernate-issues] [JIRA] Closed: (NH-793) NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-793?page=all ]
     
Sergey Koshcheyev closed NH-793:
--------------------------------

    Resolution: Incomplete

> NHybridDataReader.ReadIntoMemory fails when the result is 0 records. "Invalid attempt to read when no data is present".
> -----------------------------------------------------------------------------------------------------------------------
>
>          Key: NH-793
>          URL: http://jira.nhibernate.org/browse/NH-793
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.0.3
>     Reporter: dstefanov
>     Priority: Critical

>
> public bool Read()
> {
> 	// DS 6/30/06 - If the result is 0 records the read will always return false 
> 	// and the _isMidstream should be false so we don't attempt to read from the 
> 	// reader when we do ReadIntoMemory. We were getting an error 
> 	// "Invalid attempt to read when no data is present" when trying to get data 
> 	// from the reader is such cases.
> 	//
> 	//_isMidstream = true;
> 	//return _reader.Read();
> 	//
> 	_isMidstream = _reader.Read();
> 	return _isMidstream;
> }

-- 
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

[nhibernate-issues] [JIRA] Updated: (NH-730) make the bag Attribute protected instead of private in PersistentBag.cs

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-730?page=all ]

Sergey Koshcheyev updated NH-730:
---------------------------------

    Fix Version: 1.2.0.CR1

> make the bag Attribute protected instead of private in PersistentBag.cs
> -----------------------------------------------------------------------
>
>          Key: NH-730
>          URL: http://jira.nhibernate.org/browse/NH-730
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Beta1
>     Reporter: Franz Meier
>     Priority: Trivial
>      Fix For: 1.2.0.CR1

>
> File PersistentBag.cs
> Original:
> 	public class PersistentBag : AbstractPersistentCollection, IList
> 	{
> 		private IList bag;
> should be:
> 	public class PersistentBag : AbstractPersistentCollection, IList
> 	{
> 		protected IList bag;
> The big problem is, that if you create you own collections,
> you need to access the underlying bag!
> The PersistentSet is correct!

-- 
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

[nhibernate-issues] [JIRA] Updated: (NH-685) Support UTF-8 for class name

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-685?page=all ]

Sergey Koshcheyev updated NH-685:
---------------------------------

    Fix Version: LATER

> Support UTF-8 for class name
> ----------------------------
>
>          Key: NH-685
>          URL: http://jira.nhibernate.org/browse/NH-685
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Versions: 1.2.0.Beta1
>     Reporter: Fabio Maulo
>     Priority: Minor
>      Fix For: LATER
>  Attachments: NH685.7z, NH685Pack.7z
>
> C# support UTF-8 for class, property an method name.
> NHb are use class name for alias in SQL but no all RDBMS support UTF-8 so the SQL throw an 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

[nhibernate-issues] [JIRA] Updated: (NH-764) Create a tool to help migrate users from 1.0.2 to 1.2

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-764?page=all ]

Sergey Koshcheyev updated NH-764:
---------------------------------

    Fix Version: 1.2.0.CR1

> Create a tool to help migrate users from 1.0.2 to 1.2
> -----------------------------------------------------
>
>          Key: NH-764
>          URL: http://jira.nhibernate.org/browse/NH-764
>      Project: NHibernate
>         Type: New Feature
>   Components: Toolset
>     Versions: 1.2.0.Beta1
>     Reporter: Ayende Rahien
>      Fix For: 1.2.0.CR1

>
> Due to the amount of changes in moving from 1.0 to 1.2, a tool to aid migration would be really helpful.
> Responsabilities:
> - Update hbm.xml files:
>  - To change the schema name
>  - To add default-lazy="false" IF the user want it.
> - Check the compiled assemblies and report any proxy validation errors in bulk, so users can fix them all in one go, rather than one by one.

-- 
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

[nhibernate-issues] [JIRA] Updated: (NH-805) A Function for setting the Fetch strategy on an Object

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-805?page=all ]

Sergey Koshcheyev updated NH-805:
---------------------------------

    Fix Version: LATER

> A Function for setting the Fetch strategy on an Object
> ------------------------------------------------------
>
>          Key: NH-805
>          URL: http://jira.nhibernate.org/browse/NH-805
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Versions: 1.2.0.Beta2
>     Reporter: Franz Meier
>      Fix For: LATER

>
> and a function to query collection later by specifying a fetching strategy
> sample:
> class User
> {
>    string username;
>    Ilist UserGroups;
> }
> class UserGroup
> {
>     User user;
>     Group group;
>     ...
> }
> class Group
> {
>     string groupname;
>     IList UserGroups;
> }
> User user = session.Load<User>(1);
> session.SetFetchingStrategy(user, "UserGroups", Strategy.Select)
> session.SetFetchingStrategy(user, "UserGroups.group", Strategy.Join)
> session.FetchCollection(user, "UserGroups"); // this funktion would the init the collection 
> // of the specified user object by using my defined fetching strategy
> It think all funktion are available in the nhibernate core, somebody should only write
> the funktions

-- 
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