Win a copy of Node.js Design Patterns: Design and implement production-grade Node.js applications using proven patterns and techniques this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Upper-case required in Where Clause?

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, all. In WebSphere 4.0 Infocenter 6.6.0.15.5: Implementing custom finder helpers for CMP entity beans, I noticed that all the select statements are in upper-case but there is no mention that it has to be in upper-case. So I am wondering if the statements are to be in upper-case?
You see, I was using the where clause when I entered "(T1.userID = ?) AND (T1.companyid =?)" and this gave me a nullpointer exception which I traced it to the find method that is calling the above where clause. After trying all ways to resolve this issue, the last resort I took was to change the above where clause statement to all upper case and this is resolved.
Can anyone confirm or disprove this? For your info, I am running on Win 2000, WebSphere Advanced Edition Server and DB2. Thanks
 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
With Oracle as Database I have tested it is taking both the case and running fine.
May be this problem with DB2.
 
Jacqueline Qin
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks, Susil, for your contribution. It could be a DB2 issue as you mentioned. I noticed that DB2 is more case-sensitive than Oracle. Can anyone else confirmed this case-sensitivity issue?
 
They worship nothing. They say it's because nothing lasts forever. Like this tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic