![]() | |
![]() |
| | Thread Tools | Display Modes |
#21
| |||
| |||
|
|
I wonder if Oracle has the same behaviour? (The code needs to work with Oracle too). Oracle abstracts itself from the ANSI isolation levels; it uses a different model (MVCC).So when you say 'READ COMMITTED' in Oracle it has different semantics; i.e. it does not lock anything |
|
Ingres has MVCC too.Check <a href="http://community.ingres.com/wiki/ MVCC">MVCC wiki </a |
#22
| |||
| |||
|
|
The custom locking schemes like READLOCK etc, predate the ANSI standard and that is why the still exist? |
#23
| |||
| |||
|
|
nikosv wrote: I wonder if Oracle has the same behaviour? (The code needs to work with Oracle too). Oracle abstracts itself from the ANSI isolation levels; it uses a different model (MVCC).So when you say 'READ COMMITTED' in Oracle it has different semantics; i.e. it does not lock anything That's pretty much correct, although the isolation levels are defined in terms of anomalies that will be visible, rather than locking. |
#24
| |||
| |||
|
|
On Mar 13, 8:39*pm, Roy Hann <specia... (AT) processed (DOT) almost.meat> wrote: nikosv wrote: I wonder if Oracle has the same behaviour? (The code needs to work with Oracle too). Oracle abstracts itself from the ANSI isolation levels; it uses a different model (MVCC).So when you say 'READ COMMITTED' in Oracle it has different semantics; i.e. it does not lock anything That's pretty much correct, although the isolation levels are defined in terms of anomalies that will be visible, rather than locking. yes like in the sense that the vendor can implement the underlying locking scheme of his liking to match the anomaly described by the isolation level |
![]() |
| Thread Tools | |
| Display Modes | |
| |