100% of people found this useful
In this wiki we would like to share some issues we found when we run all NHibernate tests using a specific dialect.
The reference RDBMS for NHibernate is MSSQL.
When you find a failing test with your dialect there are various possible reasons:
- the RDBMS don't support a feature that other RDBMS support
- the implementation of the NH dialect is incomplete
- the test fail but the underling feature is supported by the dialect/RDBMS
- the test should need some adjustment to pass in your dialect
What you can do:
- Send the issue to your RDBMS bug trucker. We don't have nothing to do in NH but is useful to know the problem.
- Create the issue in our issue tracker with a candidate patch where possible.
- Nothing to do but useful to know.
- In this case you can create a patch for the test and send it to our issue tracker but in general we prefer don't touch the original test. By the way if the problem is a reserved word or the id-generator, and it is not part of the specific test, a patch is welcome.
Firebird known issues
- Criteria.CriteriaQueryTest.Subselect:
need a cast for the parameter
- GeneratedTest: test not run but the
future is supported (cause property byte array)
- Legacy.FooBarTest.ObjectType: binary
blob comparison in WHERE clause are not supported
- Legacy.MasterDetailTest.NH741:
parameter need a cast
- NHSpecificTest.NH732.Fixture: test not
ported for FB
- NHSpecificTest.NH898.NH898Fixture:
test not ported for FB
- QueryTest.MultiCriteriaFixture: not
supported feature
- QueryTest.MultipleQueriesFixture: not
supported feature
PostgreSQL known issues
- Doesn't support native Guid generation (guid.native).
- Doesn't support Schema Update.
- Doesn't support Schema Validation.