Reply from Howler_Fish on Apr 16 at 8:03 PM I believe there is also a session setting that the database link user can apply to tell MS SQL not to be case specific. I have always wondered at the design decision to say that EmpLId <> EMPLID <> emPlId. It would be interesting to see someone trying to debug this statement in a sensible manner: Select emplID, EMPlId, empliD, eMpLiD, eMPLiD from myTable, MyTable, MyTaBle, MyTabLe where myId = MyId and MYid = MYiD and myId = MYiD
| | | ---------------Original Message--------------- From: Flynn Kinkade Sent: Monday, April 16, 2012 4:05 PM Subject: Does the AppEngine SQL Editor Force SQL into Uppercase? SQL error. Stmt #: 1603 Error Position: 0 Return: 8010 - [Microsoft][SQL Native Client][SQL Server]Invalid column name 'DEF_DATE'. SELECT MAX(DEF_Date) FROM [PIGSQL2].[CSA History].[dbo].[DataEntryForms_a] Process 840927 ABENDED at Step PW_CCBANKRCN.CSA.Step01 (SQL) -- RC = 8010 (108,524) Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s My DBA has shown me that the above SQL statement is being forced into all CAPS when it hits the database. The problem is that the database PIGSQL2 is a MS Sql Server 2000 database, and the field name (as well as the record name) is in mixed case. Any thoughts on this, or how I can get around it? Thanks! | | Reply to this email to post your response. __.____._ | _.____.__ |
No comments:
Post a Comment