5 Commits (985bfeaef79ccaa32cb527e63fcbed0c8f36b1e4)

Author	SHA1	Message	Date
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171) ... [ci skip]	7 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Markus Kahl	08ee7cdcc0	don't mess things up for sqlite	9 years ago
Jan Sandbrink	067f903008	Resolve stackoverflow ... new_connection -> our patch -> determine adapter type -> ActiveRecord::Base.connection -> new_connection	9 years ago
Jan Sandbrink	fb33d8368e	Enforce default isolation level of READ COMMITTED ... This sets the session (== ActiveRecord connection) wide default transaction isolation level. Specific reason: For advisory based locking over journals in MySQL to work correctly, we need to ensure that the SELECT that determines the maximum version reads from the most recent committed data. However, by default MySQL would use REPEATABLE READ, which snapshots the database at the first SELECT of a transaction. Generic reason: Until now we did not expect any specific isolation level, this might be bad as MySQL and PostgreSQL already use different defaults. It is also possible to reconfigure a DBMS for a different default, so we would either need to require our customers to configure a specified isolation level OR we set one for our own sessions... Now we know for sure that our transactions are using READ COMMITTED unless specified otherwise on the transaction.	9 years ago