Inserting a custom History row that includes a date attribute, built for `client_sys.attr_value_to_date` to later parse back into a date, keeps coming out wrong, no matter whether `to_date(SYSDATE)` or an explicit `to_date(SYSDATE, '<format>')` is used as the input.

Q: Inserting a custom History row that includes a date attribute, built for `client_sys.attr_value_to_date` to later parse back into a date, keeps coming out wrong, no matter whether `to_date(SYSDATE)` or an explicit `to_date(SYSDATE, ' ')` is used as the input.

client_sys.attr_value_to_date expects the date to already be encoded as a specific TEXT string in its expected format, not as a genuine Oracle DATE value passed through another TO_DATE() call — build the attribute string using TO_CHAR(SYSDATE, 'YYYY-MM-DD-HH24.MI.SS'), matching the exact format the attribute-parsing framework expects, rather than any form of TO_DATE(), since TO_DATE() returns a DATE type rather than the specifically formatted string the attribute value actually needs to contain.

Answer

client_sys.attr_value_to_date expects the date to already be encoded as a specific TEXT string in its expected format, not as a genuine Oracle DATE value passed through another TO_DATE() call — build the attribute string using TO_CHAR(SYSDATE, 'YYYY-MM-DD-HH24.MI.SS'), matching the exact format the attribute-parsing framework expects, rather than any form of TO_DATE(), since TO_DATE() returns a DATE type rather than the specifically formatted string the attribute value actually needs to contain.

← Browse Developer Studio, deployment, and upgrades questions