Hi Tuna,
Actually I tried to do it, and I'm still trying... But the (not) funny
thing, is that it fails randomly in a working application since I
updated NH, and it really looks as a NH problem. I guess it might be
due to a theads problem, but I'm using the session-per-request pattern
so I shouldn''t be a problem.

I posted this just to see if any of you remember any change on any of
the involved classes.

I'll keep trying.

Thanks!,
Diego

On Mon, Dec 15, 2008 at 4:44 PM, Tuna Toksöz <[email protected]> wrote:
> Can you add a test case
>
> On Mon, Dec 15, 2008 at 8:35 PM, Diego Jancic <[email protected]> wrote:
>>
>> Hi Guys!
>> I know that bugs shouldn't be posted here, but I cannot make a test to
>> reproduce and upload it the JIRA, because it's too weird for me.
>>
>>
>> Let me explain:
>> - I updated from revision 3519 to the current revision in the trunk (3948)
>> - It wasn't failing before (it's working perfect everywhere)
>> - It starts failing 2 or 3 minutes after I use the app. Even the
>> simplest queries.
>>
>> Look the parameter numbers in the generated queries below:
>>
>>
>> exec sp_executesql N'
>>
>> select terminolog0_.Id as Id49_,
>> terminolog0_.Localized as Localized49_,
>> terminolog0_.Universal as Universal49_,
>> terminolog0_.ScopeId as ScopeId49_
>> from DB.dbo.Terminology terminolog0_
>> where (terminolog0_.univers...@p0 )and(terminolog0_.scope...@p0 )
>>      <------- HERE
>>
>> ',N'@p0 nvarchar(8),@p1 int',
>> @p0=N'Semester',@p1=2
>>
>>
>> exec sp_executesql N'
>>
>> select translatio0_.Localized as x0_0_
>> from DB.dbo.Translation translatio0_
>> where (translatio0_.univers...@p4 )and(translatio0_.cultu...@p4 )
>>      <------- HERE
>>
>> ',N'@p0 nvarchar(35),@p1 nvarchar(5)',
>> @p0=N'StandByLogs.EditWizard.SelectAClass',@p1=N'en-US'
>>
>> Obviously it's wrong, but the queries are really simple and thus I
>> don't understand what could be the problem.
>>
>> Thanks in advance for any tip!
>> Diego
>
>
>
> --
> Tuna Toksöz
> http://tunatoksoz.com
>
> Typos included to enhance the readers attention!
>
>

Reply via email to