[
https://issues.apache.org/jira/browse/TORQUE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494772
]
Brendan Miller commented on TORQUE-94:
--------------------------------------
#1 and #2 are both present in my particular case.
I have an object I would like to delete. It's not quite the way the code you
presented, but similar. In my case I either got the record using a Criteria,
or it was recently created, save()d, and now I want to delete the corresponding
row.
It also is true that this table has no primary key. And RecordPeer.doDelete()
does generate a monster where clause including every column, including the
timestamp field.
Regardless, I believe the DBOracle.getDateString() is incorrect as the
TO_DATE() function does not take into account fields defined with milliseconds
added.
> DBOracle doesn't create proper TO_DATE() clause for TIMESTAMP(6) fields
> -----------------------------------------------------------------------
>
> Key: TORQUE-94
> URL: https://issues.apache.org/jira/browse/TORQUE-94
> Project: Torque
> Issue Type: Bug
> Components: Runtime
> Affects Versions: 3.3-RC2
> Environment: Java 1.5, Oracle 9i
> Reporter: Brendan Miller
> Priority: Minor
>
> I observed when calling TablePeer.doDelete(tableObject) for an object that
> had a type="TIMESTAMP" (stored as TIMESTAMP(6) in Oracle), it would not find
> the matching row to delete. I tracked this down to the SQL that was being
> generated omitted the milliseconds.
> A row in a table with a column called 'ENTRY_TIMESTAMP' has the value:
> 18-APR-07 03.41.56.705000 AM
> as viewed by SQL*Plus. The generated SQL fragment is
> TO_DATE('18-APR-2007 03:41:56', 'DD-MM-YYYY HH24:MI:SS')
> as evidenced by DBOracle.java. This is insufficient to match the
> milliseconds which Village apparently use when inserting the record.
> To get around this, I have written my own buildCriteria() for these objects
> that excludes the timestamp fields, but this is a temporary hack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
