Have a look to the "Welcome" message of our JIRA (top left) 2009/8/20 Joe <[email protected]>
> > > That's my next step -- just wanted to see if anyone already ran into > this and might know what I'm doing wrong. I'm assuming the problem is > with me and not NH. > > > For the test case, does it have to fit into the NHibernate.Tests > solution or can I just write a quick console app test that shows the > problem? > > --Brian > > > On Aug 20, 6:34 am, Fabio Maulo <[email protected]> wrote: > > Test case in JIRA please.I mean... before create a JIRA please be sure of > > your issue proving it in a failing test. > > Thanks > > > > 2009/8/19 Joe <[email protected]> > > > > > > > > > > > > > > > > > I use QueryByExample in my application and set IgnoreCase which was > > > working fine. > > > > > But, it seems to have broken when I upgraded from NH 1.2.1 to NH 2.1. > > > > > The SQL generated appears to be the same, however, the parameters are > > > not. > > > > > Under NH 1.2.1, if I were to search for a string property with "A", > > > the parameter sent to the database was actually "a%". > > > Under NH 2.1, if I search for a string property with "A", the > > > parameter sent to the database is "A". > > > > > Am I missing something. Did this behavior change on purpose? > > > > > This is against an Oracle database, using the "Oracle9iDialect" from > > > 2.1 > > > > > Thanks for any help / pointers! > > > > -- > > Fabio Maulo > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
