Re: ar validations cannot work unless transaction isolation level is serialzable

After some digging I can tell that... not really...

MySQL(InnoDB): true
H2: true. side-effect of total absence of row-level locking,
so locks
the whole table as any DML statement would.

SQLServer: "key-range" locking supported and
effect achievable but
with different syntax (locking hints in the FROM clause)

FireBird, OpenBase, Mimer: couldn't find relevant info so
far

PostgreSQL: looks like false?
Oracle: false
FrontBase: false
Sybase: who cares, it's discontinued anyway

false because non-transactional: SQLite, Derby, hsqldb

Ok, it seems that's rather non-standard feature of MySQL. Is
it a
stopper? MySQL is so mainstream that it may be worth adding
anyway(?)


On Dec 22, 1:27 am, "Jeremy Kemper" <jer...bitsweat.net> wrote:
> That's cool. I thought FOR UPDATE wouldn't prevent
inserts. Is this
> also true for the other databases we support?
>
> jeremy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Ruby on Rails: Core" group.
To post to this group, send email to rubyonrails-coregooglegroups.com
To unsubscribe from this group, send email to
rubyonrails-core-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---