RE: [CFCDev] OT: CFMX 6.1, Oracle 8.05, CreateODBCDateTime()

[Brad Howerter]

Title: Message

I ran sql trace on the coldfusion connection to oracle, then looked at the trace file:   <cfquery datasource=...>     ALTER SESSION SET SQL_TRACE = TRUE </cfquery>   You can shut it off with FALSE -----Original Message----- From: Davis, Eric [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 11:34 AM To: '[EMAIL PROTECTED]' Subject: RE: [CFCDev] OT: CFMX 6.1, Oracle 8.05, CreateODBCDateTime() We've decided to code the date format ourselves:   {ts '#DateFormat(foo, 'yyyy-mm-ss')# #TimeFormat(foo, 'HH:mm:ss')'}   I'll let you know what the results are.   I'd still like to get to the bottom of why the function no longer works in Oracle 8. What would make Macromedia change their call to a version-specific database function? This just seems sloppy to me. And Brad, how did you figure out exactly what the SQL call was?   Thanks for your help, all. -- Eric C. Davis Programmer/Analyst I Georgia Department of Transportation Office of I.T. Applications Web Applications Group 404.463.2860.199 [EMAIL PROTECTED] -----Original Message----- From: Jeff Britts [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 1:27 PM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] OT: CFMX 6.1, Oracle 8.05, CreateODBCDateTime() Change your queryparam type to CF_SQL_TIMESTAMP. -----Original Message----- From: Brad Howerter [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 12:17 PM To: '[EMAIL PROTECTED]' Subject: RE: [CFCDev] OT: CFMX 6.1, Oracle 8.05, CreateODBCDateTime() The query doesn't work correctly.  It doesn't error, but it seems to treat the value as just a time stamp with no date part.   This query returns 0 rows:   <cfquery name="rs" datasource="#request.dsn.select#">  SELECT * FROM DUAL WHERE SYSDATE - 1 < <cfqueryparam value=#createODBCDateTime(now() )# cfsqltype="CF_SQL_TIME"> </cfquery> -----Original Message----- From: Stacy Young [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 7:52 AM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] OT: CFMX 6.1, Oracle 8.05, CreateODBCDateTime() What happens if u use cfqueryparam and use "timestamp" data type?   -----Original Message----- From: Davis, Eric [mailto:[EMAIL PROTECTED] Sent: September 4, 2003 9:35 AM To: [EMAIL PROTECTED] Subject: [CFCDev] OT: CFMX 6.1, Oracle 8.05, CreateODBCDateTime()   When used together, CFMX 6.1, Oracle 8.05, CreateODBCDateTime() error out. The same code works fine in CFMX 6.0. Can anyone verify? The code in use is: --- <cfquery name="getOperator" datasource="mva">         SELECT  oper_name, (etc)         FROM    mva_assignment         WHERE   x_datetime_insert = #CreateODBCDateTime(url.dt)#                 AND (etc) </cfquery> --- The exact error returned is: --- Error Executing Database Query. ORA-00904: invalid column name --- The odd thing is that if the call is changed to CreateODBCDate(), it no longer errors out; the field is, however, a datetime field. I'm not sure if this is a driver issue or a JDBC-ODBC Bridge issue, or some other issue entirely. I'm just looking for help for a colleague. Has anyone run into this? -- Eric C. Davis Programmer/Analyst I Georgia Department of Transportation Office of I.T. Applications Web Applications Group 404.463.2860.199 [EMAIL PROTECTED] AVIS IMPORTANT: ------------------------------- Les informations contenues dans le present document et ses pieces jointes sont strictement confidentielles et reservees a l'usage de la (des) personne(s) a qui il est adresse. Si vous n'etes pas le destinataire, soyez avise que toute divulgation, distribution, copie, ou autre utilisation de ces informations est strictement prohibee. Si vous avez recu ce document par erreur, veuillez s'il vous plait communiquer immediatement avec l'expediteur et detruire ce document sans en faire de copie sous quelque forme. WARNING: ------------------------------- The information contained in this document and attachments is confidential and intended only for the person(s) named above. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution, or any other use of the information is strictly prohibited. If you have received this document by mistake, please notify the sender immediately and destroy this document and attachments without making any copy of any kind.