No worries Henry. Unfortunately for Jordan, I'm not willing to pollute my dev machine with SQL Server, otherwise I would have done it.
Cheers John ________________________________ From: Henry Conceição <[email protected]> To: [email protected] Sent: Tuesday, 15 March 2011 10:30 AM Subject: Re: Readonly transactions - yet again. John, Since from the begging I'm against to add this feature to the tx support. I do concur that nh read only sessions are usefull (and at some situations mandatory), but for me, read only transactions in the way that Transactions are know in the .net platform doesn't makes sense. If you guys want to push a way to expose the read only session without mixing it with the tx facility, I'm here to help. But for this tx read only stuff, it's up to you guys to get it up and running. Cheers, Henry Conceição On Mon, Mar 14, 2011 at 8:09 PM, John Simons <[email protected]> wrote: > Henry, > > Since you are most familiar with NH facility + the new NH readonly feature, > can u review the patch, and if no good, re-write it to use the native nh > api? > Unless Tuna Toksoz is still looking after this facility? > Cheers > John > > > > ________________________________ > From: Henry Conceição <[email protected]> > To: [email protected] > Sent: Tuesday, 15 March 2011 10:04 AM > Subject: Re: Readonly transactions - yet again. > > If it uses the functionality provided by nhibernate, yes. Otherwise, > will lead to wrong assumptions. > > Cheers, > Henry Conceição > > > > On Mon, Mar 14, 2011 at 7:58 PM, John Simons <[email protected]> > wrote: >> Henry, >> All I'm after is someone that can merge + run the unit tests locally >> against >> a sql server instance. >>>Also, Nh nows support read only sessions natively. That should be useful >>> in >>> scenarios like this. >> Cool, so this change makes more and more sense then :) >> >> Cheers >> John >> >> >> >> ________________________________ >> From: Henry Conceição <[email protected]> >> To: [email protected] >> Sent: Tuesday, 15 March 2011 9:24 AM >> Subject: Re: Readonly transactions - yet again. >> >> Also, Nh nows support read only sessions natively. That should be >> useful in scenarios like this. >> >> Cheers, >> Henry Conceição >> >> >> >> 2011/3/14 Henry Conceição <[email protected]>: >>> By new I meant the 2.5.3 version. >>> >>> Cheers, >>> Henry Conceição >>> >>> >>> >>> 2011/3/14 Henry Conceição <[email protected]>: >>>> To release the nh facility with these changes, I would have to release >>>> the tx stuff first, and this is not on my schedule. I will only >>>> release a update for the tx facility, with the new Windsor. >>>> >>>> Cheers, >>>> Henry Conceição >>>> >>>> >>>> >>>> On Mon, Mar 14, 2011 at 6:42 PM, John Simons >>>> <[email protected]> >>>> wrote: >>>>> 2/3 projects are merged :) >>>>> >>>>> The only outstanding project is >>>>> Castle.Facilities.NHibernateIntegration. >>>>> The reason I didn't do that one is because it requires me to have >>>>> access to some a sql server database :( No in-memory tests! >>>>> Could someone with access to a sql server merge >>>>> >>>>> >>>>> https://github.com/castleproject/Castle.Facilities.NHibernateIntegration/pull/1 >>>>> >>>>> Henry, it looks like you are getting ready to do a release? Can u >>>>> please include this pull request. >>>>> >>>>> Cheers >>>>> John >>>>> >>>>> >>>>> On Mar 7, 1:55 pm, hammett <[email protected]> wrote: >>>>>> It's OK for a resource to not support readonly semantics. In this case >>>>>> the >>>>>> resource should either mimic the behavior artificially or throw an >>>>>> exception. >>>>>> >>>>>> On Sun, Mar 6, 2011 at 2:23 PM, John Simons >>>>>> <[email protected]>wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> > Jordan, >>>>>> > I'm not merging your pull request because of the concerns raised by >>>>>> > Henry. >>>>>> >>>>>> > Henry, >>>>>> > I let u take over this one, since u know a lot more about these >>>>>> > Components/Facilities than me. >>>>>> >>>>>> > Cheers >>>>>> > John >>>>>> >>>>>> > On Mar 3, 8:34 pm, Jordan <[email protected]> wrote: >>>>>> > > > I think I just found it: >>>>>> >http://github.com/castleproject/Castle.Services.Transaction/pull/1 >>>>>> >>>>>> > > > Is this it? >>>>>> >>>>>> > > Yes, also these 2: >>>>>> >>>>>> >>>>>> > >>>>>> > > >https://github.com/castleproject/Castle.Facilities.NHibernateIntegrat.... >>>>>> > .. >>>>>> >>>>>> > > There was one change Hammett pointed out needed to be made in this >>>>>> > > file: >>>>>> >>>>>> > >>>>>> > > >https://github.com/gusgorman/Castle.Facilities.NHibernateIntegration/... >>>>>> > > where the call to ResetFlushMode() shouldn't be from within the ! >>>>>> > > isAmbient clause. >>>>>> >>>>>> > > many thanks, >>>>>> > > Jordan. >>>>>> >>>>>> > -- >>>>>> > You received this message because you are subscribed to the Google >>>>>> > Groups >>>>>> > "Castle Project Development List" 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/castle-project-devel?hl=en. >>>>>> >>>>>> -- >>>>>> Cheers, >>>>>> hammetthttp://hammett.castleproject.org/ >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Castle Project Development List" 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/castle-project-devel?hl=en. >>>>> >>>>> >>>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Castle Project Development List" 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/castle-project-devel?hl=en. >> >> >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Castle Project Development List" 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/castle-project-devel?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" 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/castle-project-devel?hl=en. > > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" 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/castle-project-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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/castle-project-devel?hl=en.
