[Home] [Help]
1853: ----------------------------------------------------------------
1854: -- Now we rely on dynamic SQL to treat the bound string as an --
1855: -- expression for a Date object, and we call TO_CHAR on it to --
1856: -- turn it into a string version of that Date, formatted into --
1857: -- our standard format. --
1858: ----------------------------------------------------------------
1859: l_dynamic_sql := 'SELECT TO_CHAR('||l_formatted_string||', '''||
1860: EGO_USER_ATTRS_COMMON_PVT.G_DATE_FORMAT||''') FROM DUAL';
1861: Debug_Msg('In Format_Sysdate_Expression, l_dynamic_sql is as follows:', 3);
2154: ASSUMPTIONS:
2155: 1). the UI validates that Number default values with UOM are in the UOM base
2156: 2). the UI validates that Date default values are in
2157: EGO_USER_ATTRS_COMMON_PVT.G_DATE_FORMAT and that
2158: Standard Date default values are truncated appropriately
2159: ***/
2160:
2161: l_candidate_value := l_default_value;
2162:
10650:
10651: EXCEPTION
10652:
10653: ----------------------------------------------------------------------------
10654: -- We do not ROLLBACK in this procedure: standard behavior for Business --
10655: -- Objects is for each row being processed to succeed or fail independent --
10656: -- of the status of other rows, so we let Process_Row ROLLBACK any errors --
10657: -- it encounters. If callers want different behavior, they can establish --
10658: -- a SAVEPOINT prior to calling this procedure and ROLLBACK if we report --