Thanks for clarifying, I missed that point. I'll probably be going with SQL Server, but I'll try patching the dialect as a learning exercise.
On Aug 4, 7:04 am, Diego Mijelshon <[email protected]> wrote: > Um... reread my mail. > I just suggested a way to use just a patched _dialect_ with a public build. > Dialect are pluggable. > > Diego > > > > On Tue, Aug 3, 2010 at 21:27, Tim Hoolihan <[email protected]> wrote: > > Fair enough, thanks for the info. I had been waffling on Sql Server > > or MySQL anyway, as both are available at the host I'm using. So I > > may just go SQL Server for now. Not that patching sounds too > > intimidating, but I'd rather have a public release of NH than a custom > > build in the app. > > > On Aug 3, 2:28 pm, Diego Mijelshon <[email protected]> wrote: > > > You can apply the patch in the source, extract the dialect, rename it and > > > use it with NH3Alpha1 right now... > > > > Diego > > > > On Tue, Aug 3, 2010 at 13:10, Tim Hoolihan <[email protected]> > > wrote: > > > > [...] > > > > but as that bug report points out, the other statement should be a > > > > valid cast. Any chance that patch will be applied to 3.0 soon? > > > -- > > You received this message because you are subscribed to the Google Groups > > "nhusers" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<nhusers%[email protected] > > > > > . > > For more options, visit this group at > >http://groups.google.com/group/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
