That must be something trivial, or at least that's what I usually end up with when I struggle on stuff like this after going down the 'select is broken' path. 2009/10/7 Ayende Rahien <[email protected]>
> I can't figure out what is going on there yet, it is REALLY strange. > > 2009/10/7 Simone Busoli <[email protected]> > > That's pretty weird, I think thousands of people are doing the same all >> over the world, or am I missing something which makes this case special? >> >> 2009/10/7 Ayende Rahien <[email protected]> >> >> That is a bug, investigating where the issue is now >>> >>> 2009/10/7 Vadim Kantorov <[email protected]> >>> >>> >>>> Uploaded a repro. It presumes you have an sql express instance on your >>>> machine (if not, please go to the DefaultDatabaseConfiguration file to >>>> change) and "bugs" database created with enabled trusted connection. >>>> >>>> On 8 окт, 00:48, Vadim Kantorov <[email protected]> wrote: >>>> > Ok, I have an idea how to reproduce ;) >>>> > Instead of creating a new project, I'll copy this one and remove all >>>> > the rubbish :) >>>> > >>>> > On 8 окт, 00:23, Ayende Rahien <[email protected]> wrote: >>>> > >>>> > >>>> > >>>> > > Can you create a unit test to reproduce the problem?This scenario is >>>> known >>>> > > to work correctly (at least I think so, I wrote a test for something >>>> > > similar). >>>> > >>>> > > 2009/10/7 Vadim Kantorov <[email protected]> >>>> > >>>> > > > Helped. Ridiculous. >>>> > > > Oren, I would like the session to be enlisted in the transaction, >>>> so >>>> > > > it is ok, isn't it? >>>> > >>>> > > > I still have no clue what this exception means and what are the >>>> > > > internal reasons.. >>>> > > > Oren, if you do, could you please explain further a little bit. >>>> > >>>> > > > I wonder if it is me who screwed up or it is NH or whatever that >>>> is >>>> > > > buggy. >>>> > >>>> > > > On 7 окт, 23:37, Corey Kaylor <[email protected]> wrote: >>>> > > > > Not sure which Dialect is being used, but if it's SQL Server >>>> we've had >>>> > > > > issues with the enlistment of transactions in NHibernate and >>>> changed our >>>> > > > > settings to use the property below. I hadn't had time to track >>>> down >>>> > > > exactly >>>> > > > > why the default transaction factory had issues, but regardless >>>> for us >>>> > > > this >>>> > > > > fixed our issues. >>>> > > > > .SetProperty(Environment.TransactionStrategy, >>>> > > > > "NHibernate.Transaction.AdoNetTransactionFactory") >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
