Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re^13: SQL query using elements from array

by mje (Curate)
on Oct 29, 2014 at 11:57 UTC ( [id://1105446]=note: print w/replies, xml ) Need Help??

in reply to Re^12: SQL query using elements from array
in thread SQL query using elements from array

If you look at your schema you are trying to select rows based on a timestamp but the column AuditChrt_TimeStamp is a char(10). That is not going to work.

The very first snippet of code you showed was binding '2013-08-01 00:00:00.000' which is also way too big for a char(10). I incorrectly assumed you actually had a timestamp column. In the future it sould save time if you provided the schema at the same time.

  • Comment on Re^13: SQL query using elements from array

Replies are listed 'Best First'.
Re^14: SQL query using elements from array
by poj (Abbot) on Oct 29, 2014 at 12:22 UTC
    The output shown has been reformatted with line breaks, I think the schema is
    AuditChrt_ID 1 char 10 AuditChrt_RecordState 2 tinyint AuditDgphAlias_ID 3 char 10 AuditDgphType_ID 4 char 10 Login_ID 5 char 10 AuditChrt_Description 6 varchar 400 AuditChrt_Update 7 bit AuditChrt_RecordID 8 char 10 AuditChrt_TimeStamp 9 datetime AuditChrt_RowGuid 10 uniqueidentifier Patient_ID 11 char 10 AuditChrt_Workstation 12 varchar 40 AuditReason_ID 13 char 10 AuditMedication_ID 1 char 10 AuditMedication_RecordState 2 tinyint AuditDgphAlias_ID 3 char 10 AuditDgphType_ID 4 char 10 Login_ID 5 char 10 Pharmacy_ID 6 char 10 AuditMedication_Description 7 varchar 400 AuditMedication_Update 8 bit AuditMedication_RecordID 9 char 10 AuditMedication_TimeStamp 10 datetime AuditMedication_SendMethod 11 tinyint AuditMedication_RowGuid 12 uniqueidentifier Patient_ID 13 char 10 AuditMedication_Workstation 14 varchar 30

      Yes, my mistake, sorry, it does in fact look like it is a datetime and a datetime in MS SQL Server is compatible with an ODBC quoted ts.

      However, it appears I've somewhat mislead you. The SQL Server driver I use does accept ODBC timestamp escapes in bound parameters whereas the MS one appears not to. So, if you are using the ODBC escapes with your driver you'd need to concatenate them into your SQL or pass them as plain timestamp strings in a format MS accepts.

        OK, thanks I will try that, once again thank you for all your time and effort!

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1105446]
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (6)
As of 2024-04-23 11:17 GMT
Find Nodes?
    Voting Booth?

    No recent polls found