Hibernate version:1.0.2

I read this in another post:

"... if you just retrieve the latest version of nH through subversion, you have generics by nh. It's not a fullly tested implementation, but works for me"

I think there are just to many items in JIRA for the next version of NHibernate, and seems to me that implementing and fixing all the issues will take a lot of time.

I can't retrieve the latest version of NHibernate through subversion due to some firewall restrictions and doing it manually (by using the browser) would take very long.

If generics are almost ready, being a VERY popular issue, why not release a minor version update with current finished work and generics?

Who's with me?

I'll see what I can do. The thing is, until recently the most popular issue was stored procedures support, but now the user priorities seem to have reversed with generics getting like 50 votes, so I will have to adapt, I guess.

There is support for generics, just not yet natively through NHibernate. Check out http://www.codeproject.com/useritems/NH ... ctices.asp for more info and an example of how to set it up.

I've been using this intermediary solution without any problems and it should take a VERY small effort to convert to the native NHibernate usage of generics once it's supported.

Billy

Even with other alternatives to support generics with NHibernate official support is what a lot of people is waiting for.

I was testing Ayende's dlls with ICollection, but ICollection doesen't allow me to reference the array with an index like an ArrayList.

eg:



Will NHibernate generics support other collection types?

I think hector means, if the work on generics is done, and NHibernate SVN works with generics natively, then it should be released.

I think he would rather use the NHibernate native generic functionality rather than another solution to hack in generics. (No offense intended to the other generic solutions)

***

My personally, I am playing with the SVN NHibernate version to see how it works and see if I can get my project ready to take advantage of it when it comes out officially. I had to change some of my mappings and objects to get SVN NHibenate to work --- because they were not done right the first time.

So hopefully when NHibernate supports generics natively, my project will already be able to use it.

You got it Pelton, that's what I mean!

I have tried Ayende's generics, but I also need a generic dictionary in one project and would love to have this functionality natively from NH.

Yeah, definitely agreed...I'm looking forward to native support myself.

Hi wmccafferty,

Actually, you can substitute EntityList<T> for of EntitySet<T> so that you can use IList<T> rather than ICollection<T>. EntityList<T> works with NHibernate bag mappings.

Don't know if this helps - it's not in the documentation, but I've been using it without any trouble.

Cheers,

Symon.

Sorry,

That last post was meant for cassiot - my mistake. I do miss having the edit feature on these posts...

Symon.

But.... I have been able to edit my posts...

EDIT: Just for proof of concept... <grin>

Gert

Doh!

Well there you go - when they moved the forum over here there wasn't an edit function. Since then I've been too blind to even notice that it's re-appeared!

Thanks for the pointer...

Symon.

It worked Simon. I didn't realize that. I thought that EntityList was to use with <list>.

Thank you.

MY ARGUMENTS FOR A URGENT GENERICS .NET 2.0 NHibernate RELEASE:

Argument 1

I checked today the popular issues on JIRA, and the ranking is:

1) With 48 votes: Generics (.NET 2.0)
2) With 18 votes: Type-safe collections (aka generics)
3) With 15 votes: Stored Procedures

Issue 1 and 2 are really only one issue: GENERICS (with 66 votes) against 15 for stored procedures.

Argument 2

If you check the .NET Framework version poll almost 80% of NHibernate users are using .NET 2.0 and another 15% are planning to use .NET 2.0 in the short-mid term. I think the next version of NHibernate should be a .NET 2.0 library and 95% of the users will be happy!!! (.NET 1.1 users can still use NH 1.0.2)

Argument 3
Most of the code neaded is already in Subversion and it's not so complicated. I think Stored Procedures is far harder to implement than generics.

SO: Why not make the final effort to complete the existing code if something is missing, test the existing code, document it and RELEASE IT?

Thanks,

Hector Cruz

The best way to achieve your goal might be to fix your firewall or find somewhere else to download the code and go ahead and do some of this yourself!

I am guessing that most of the 48 people voting for generics (including me) are making do right now without or are using one of the known alternatives. (However there is no public workaround for no full stored proc integration....)

Cheers,
-Matthew Hobbs

I'm not sure anything should be released as urgent unless it is a bug fix. While I support a release of NHibernate with generics, I don't believe there is that sense of urgency for it.



Does anyone else think these numbers are low? Do they really represent a majority of the NHibernate users? I would think there are more than 50 or so interested developers in the direction of NHibernate.

I don't refute your arguments, because the numbers seem to indicate strong support for generics. I just am curious if the numbers themselves reflect the will of the majority of users.



I think its hard to complain or put pressure on the NH developers, because, we're getting a very good tool for basically free. So, I would hope they can see the desire for generics to be a genuine request. But I don't think we should expect them to snap to our wishes and drop whatever it is they are working on at present.

I totally agree that I would like to see an NH generics release, but I would like to see it done in an non-knee-jerk-reaction mode.

My two cents.

--Brian