此内容已被标记为最终。 显示 6 条回复
in older apex version,
the error was "Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-20001: ORA-20001: Current version of data in database has changed since user initiated update process" .
the message is now more elegant
but i'm the only one on this sample and i have the message each time a validation fails .
any help would be very appreciate.
i can reproduce the problem on apex.oracle.com
for the sample tabular form,
if i change in globalization the Application Primary Language from english(en) to French(France) fr .
I've got the same issue here, do you have any update?
Apex 4.2, Application Primary Language set to French (Canada)(fr-ca).
In my case I've done some test and here is what I've found:
In a Tabular Form with a numeric field, if there is a value with a comma (ex: 12,5) in it, any validation who triggers on any other field will cause the error "Current tabular form data is too old".
If all the numerics are whole numbers, no problem.
Also, if I change the Application Primary Language to English (United States)(en-us) everything is fine.
Same thing whith a date field, if there is a date in the field, if a validation fires, same error message. If I specify a Date Format or If I set the Application Primary Language to English (United States)(en-us) everything is fine again.
I've got the same behavior on apex.oracle.com.
Our Apex version is 4.2.0.00.28.
Thanks JM for the update.