Hi all,

Firstly, I wanted to congratulate you all on a great framework.

We are builting a customizable web product, and have selected NHibernate 1.2-alpha as our persistence framework. I look forward to contributing to the community in the future.

1.2-alpha has some very important features (native generic support) that was cause for the decision to continue with this version.

Are their any major cautions for using this version - besides it's alpha status? We will be testing it very extensively ourselves, and will be able to raise bugs and contribute back to the community.

Cheers,

Stu

Basically, it's alpha for several reasons:
- There are some features left that I would like to add to it.
- All the tests that are there pass, but it's likely that there are still errors because the tests don't cover everything.

I have no qualms about shipping it with my personal projects, but I haven't written anything that might hit the fringe cases.

repeat:ignore

Understood.

Perhaps where feature fits our needs for our first release, we can contribute? back to the base framework? We have a very tight schedule - feature complete in Jan - which will limit the changes we can make and spend time developing.

I don't see a need in our first release, but I am very willing to port the v3.x HSQL parser to .NET and registerFunction API - this would be a key feature for us, since our platform requires support for multiple DB backends.

I ran antlr and generated a C# parser from hql.g last night, and will probably test the remaining grammars. If it looks promising, I'll look at converting the ./hql/ast folder and adding the QueryTranslatorFactory api to be compatible with 3.x. Thoughts?

If you could do that (port ANTLR grammar), it would be great. But I don't think that just porting the grammar will be enough, you would probably have to port a lot of code that the parser depends on as well.