Timeline for Understanding of Oracle Statement-Level Read Consistency between Oracle 10g and 10g+
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2021 at 11:30 | vote | accept | Just a learner | ||
| Jun 15, 2020 at 9:05 | history | edited | CommunityBot | Commonmark migration | |
| Aug 5, 2019 at 8:05 | answer | added | Albert Godfrind | timeline score: 3 | |
| Aug 5, 2019 at 8:01 | comment | added | Albert Godfrind | The important point is that the default isolation used by Oracle (statement-level consistency) implies that repeating the same statement may not deliver the same result since other transactions may have updated the data during the first execution of the statement. | |
| Aug 5, 2019 at 7:59 | comment | added | Albert Godfrind | The behaviour did not change. It has been the same since Oracle 7 at least (probably before, but that was before my time) and still is today. The documentation was just expanded to include the behaviour at isolation levels other than the default READ COMMITTED, or when using the Flashback Query mechanism. | |
| Aug 5, 2019 at 5:45 | comment | added | user1822 | I don't think Oracle changed the behaviour. The "read only" and "serializable" levels were available in Oracle 10g as well. My guess is, that they just extended the documentation on this behaviour. | |
| Aug 5, 2019 at 5:33 | history | edited | Just a learner | CC BY-SA 4.0 | added 91 characters in body |
| Aug 5, 2019 at 4:49 | history | asked | Just a learner | CC BY-SA 4.0 |