Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > LLBLGen Pro Runtime Framework> Case Sensitivity - LLBLGen 2.6.
 

Pages: 1
LLBLGen Pro Runtime Framework
Case Sensitivity - LLBLGen 2.6.
Page:1/1 

  Print all messages in this thread  
Poster Message
mshe
User



Location:
Markham, Canada
Joined on:
02-Feb-2006 23:31:34
Posted:
167 posts
# Posted on: 25-Sep-2009 22:31:12.  
Hello Everyone,


We have a SQL Server with case-insensitivity... is there a way to make LLBLGen perform, case sensitive queries - in particular with password searches?

I see there is a CaseSensitiveCollation property... but it's supposed to be used to enable case insensitive queries?

Any way of making LLBLGen Case "selectively" case sensitive?

Thanks!
  Top
daelmo
Support Team



Location:
Guatemala City
Joined on:
28-Nov-2005 23:35:24
Posted:
8088 posts
# Posted on: 26-Sep-2009 05:12:06.  
Normally the people wants: from case-sensitive to case-sensitive queries.

The thing is, LLBLGen will translate the predicates into sql code. So, ultimately the query willl run in your _case-insensitive_ server.

What if you collate your specific table to case-sensitive.


David Elizondo
LLBLGen'ing (articles and code snippets) | linkedin | twitter
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37645 posts
# Posted on: 26-Sep-2009 13:13:48.  
The predicates have no notion of case sensitivity. So if you pass in a value 'Foo' and also a value 'foo' and you use it in a predicate on a case sensitive db, it will give different results. On a case insensitive db, it will give the same results.

The case-sensitive collaction property is meant to signal that the predicate is to be used in a case sensitive collaction environment, and you want to mitigate that fact, so UPPER() is added to make it act as if case insensitive. The property name is perhaps a bit ambiguistic.

What you want can only be achieved with a case sensitive collaction (as the filtering is done by the db, which thus means it has to use case-sensitive logic). In sqlserver you can achieve case sensitive collations by defining them on the catalog, table or field. So if you give your password field a case sensitive collation it should work without you changing any llblgen pro query code Regular Smiley
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.