I've been systematically hunting down the SQLite unit test failures
and either ignoring them if they're not reasonably supportable or
adding to the dialect or NHibernate when possible. So far I've fixed
about 20 tests. Only 54 to go now.
Can't say I know what's going on with Firebird... it has tons of
failing tests. I also don't understand what's causing the current
failures. Granted, I haven't tried running the join tests locally,
nor have I dug into it. I'm much more interested in SQLite and
PostgreSQL, since those are the DBs I use.
I did add a TestDialect for things that are tested, but aren't
important to NHibernate itself. For example, NHibernate itself
doesn't care if the "= all (subquery)" operator is available, but some
unit tests test that operator specifically.
I'm still awaiting the installation of PostgreSQL on the teamcity
server. Looking forward to seeing that run all the tests as well.
Does anyone want to adopt any other dialects? :) I volunteer to
watch over PostgreSQL and SQLite.
Patrick Earl
On Fri, Mar 4, 2011 at 8:42 PM, Fabio Maulo <[email protected]> wrote:
> I have fixed similar problems long time ago, probably its a matter of
> some column name.
> btw... we have to take care ignoring tests for a specific Dialect
> because the problem can be in the dialect/driver/... and not in a not
> supported feature by RDBMS.
> Have you found the problem with SQLite?
>
> --
> Fabio Maulo
>
>
> El 04/03/2011, a las 21:06, Patrick Earl <[email protected]> escribió:
>
>> I ran the Firebird test again on the teamcity server, and it still
>> failed. I have to wonder if there really were problems introduced in
>> the latest commit. Does anyone recognize what might be the issue
>> here?
>>
>> This file has the list of failing tests at the bottom.
>>
>> http://teamcity.codebetter.com/repository/download/bt324/22193:id/NHibernate-3.1.0.GA-debug/bin/net-3.5/test-results/Comparison.txt
>>
>> Patrick Earl
>
