SchemaUpdate fails for Firebird in released binaries only - NHibernate source and local builds from this source work fine

Description

Executing SchemaUpdate.Execute(true, true) throws a FirebirdSql.Data.FirebirdClient.FbException exception "Dynamic SQL Error\r\nSQL error code = -104\r\nToken unknown - line 3, char 29\r\n.". This occurs in 2.0.0Beta1 and 2.0.0Alpha2 binaries but did not occur from NHibernate source or builds made locally. Older versions of the source work as well so this appears to be a build problem.

Environment

None

Attachments

Activity

Show:

Fabio Maulo July 3, 2008 at 8:06 AM

We have a branch for NH2.0.x release.
The branch not include the new improvement of SchemaUpdate, I mean that in NH2.0.x schemaUpdate is partially supported only for MSSQL.
The trunk (next mayor version NH2.1.x) include the improvement.
I don't exactly know when we will release NH2.1.

Ben Leighton July 2, 2008 at 10:43 PM

Sorry I meant "Is there a roadmap/timeframe for incorporating this functionality into a release or into the branch"

Ben Leighton July 2, 2008 at 10:40 PM

Thanks Fabio,

If it works in the trunk then your builds are being made off a branch? I ask because I'm pretty sure that running the off the trunk prior to the release of Beta1 still worked and yet when Beta1 was released the code wasn't working.

Is there a roadmap/timeframe for incorporating this functionality from the branch.

Thanks again and also for all your great work on NHibernate.

Ben Leighton July 2, 2008 at 10:32 PM

Illustrates the problem (I hope)

Fabio Maulo July 2, 2008 at 10:28 PM

Uuhhh I understand what is the problem... I'm sorry.
The SchemaUpdate of NH2.0.0 support only MSSQL.
Probably it work in your working copy because it is the trunk and, in the trunk, we support Firebird too and potentially other dialects.

Please confirm it.
Thanks.