When a display only item with a date column as source has no formatmask an implicit charater/date conversion is done when the database checksum is calculated.
In apex 4.2 there is a difference between wwv_flow.show and wwv_flow.accept in the number of times the following is done.
Setting NLS_DATE_FORMAT to application date format: DD-MM-YYYY
...NLS: Set g_nls_date_format="DD-MM-YYYY"
...NLS: Set g_nls_timestamp_format="DD-MON-RR HH.MI.SSXFF AM"
...NLS: Set g_nls_timestamp_tz_format="DD-MON-RR HH.MI.SSXFF AM TZR"
Especially there is an extra one after the code of Security > Database session > Initialization PL/SQL Code is execute.
If there is a change of NLS_TERRITORY within this code which would result in a different formatmask implicit charater/date conversions will differ between the show and accept of a page.
The result is a database has changed error when ever a page is saved with a date display item without a formatmaks.
This didn't happen in older versions of apex.
Is this difference done deliberately?
Are only the date/time settings set an extra time or also the numeric charater settings?
[url http://apex.oracle.com/pls/apex/f?p=VANBAREN_FORUM_TRY_OUT_DUTCH:SHOWACCEPT:0&c=VANBAREN]See here for a demonstration of the issue.