Date format for Task Predicate Query

Question

Does anyone know the correct format the task query is expecting when testing against flex field data e.g. dateAttribute1?
I the following query ->
<tas1:taskListRequest xmlns:com="http://xmlns.oracle.com/bpel/workflow/common" xmlns:tas="http://xmlns.oracle.com/bpel/workflow/taskQuery" xmlns:task="http://xmlns.oracle.com/bpel/workflow/task" xmlns:tas1="http://xmlns.oracle.com/bpel/workflow/taskQueryService">
    <tas:taskPredicateQuery startRow="0" endRow="200">
      <tas:displayColumnList>
        <tas:displayColumn>textAttribute1</tas:displayColumn>
        <tas:displayColumn>textAttribute2</tas:displayColumn>
        <tas:displayColumn>textAttribute3</tas:displayColumn>
        <tas:displayColumn>textAttribute4</tas:displayColumn>
        <tas:displayColumn>numberAttribute1</tas:displayColumn>
        <tas:displayColumn>dateAttribute1</tas:displayColumn>
      </tas:displayColumnList>
      <tas:optionalInfoList>
        <tas:taskOptionalInfo>Payload</tas:taskOptionalInfo>
      </tas:optionalInfoList>
      <tas:predicate>
        <tas:assignmentFilter>All</tas:assignmentFilter>
        <tas:clause joinOperator="AND" ignoreCase="true">
          <tas:column>STATE</tas:column>
          <tas:operator>EQ</tas:operator>
          <tas:value>ASSIGNED</tas:value>
        </tas:clause>
        <tas:clause joinOperator="AND">
          <tas:column>TITLE</tas:column>
          <tas:operator>EQ</tas:operator>
          <tas:value>Index Case</tas:value>
        </tas:clause>
        <tas:clause joinOperator="AND">
          <tas:column>dateAttribute1</tas:column>
          <tas:operator>BEFORE</tas:operator>
          <tas:value>2014-12-05T12:00:00</tas:value>
        </tas:clause>
      </tas:predicate>
    </tas:taskPredicateQuery>
  </tas1:taskListRequest>
And get the following error ->
<taskQueryServiceFaultResponse  xmlns="http://xmlns.oracle.com/bpel/workflow/taskQueryService">
      <message>
           ORA-30961:Invalid value specified in predicate clause.
          The value 2014-12-05T12:00:00 for column wfn.dateAttribute1 is invalid for the columns  data type.
          Specify a value that is of the correct type, or is another column with a matching  data type.
      </message>
</taskQueryServiceFaultResponse>
I have tried a number of formats and always get the same error!

Answer 1

Of course you're right, thor_b. My point is that Oracle's "to_date" can convert a string to a date, but that's not how Access or SQL Server or any other RDBMS do it. They're all different. If you hardwire "to_date" into your SQL you'll have to rewrite the whole thing if you move from Oracle to SQL Server.
I like the PreparedStatement because it takes care of all that for me.
Performance penalty? Over Statement? I've read some stuff about that, but I find it hard to believe.
Whenever you send SQL to a relational database it has to parse the SQL, determine if the tables and columns exist and have the right types, optimize the query, and then execute it. You have to do that whether you're using Statement or PreparedStatement. If PreparedStatement allows the RDBMS to do all that work once and then store it, I can't see how you'll do worse. - MOD