RE: Default mode for transaction in postgreSQL and J DBC
От | Peter Mount |
---|---|
Тема | RE: Default mode for transaction in postgreSQL and J DBC |
Дата | |
Msg-id | 1B3D5E532D18D311861A00600865478CF1B005@exchange1.nt.maidstone.gov.uk обсуждение исходный текст |
Список | pgsql-interfaces |
The driver included in 6.5.3 is actually the 6.5.2 one (due to me not committing it correctly). In the 7.0, the transactionIsolation() code was implemented as part of the javax.sql extensions. -- Peter Mount Enterprise Support Maidstone Borough Council Any views stated are my own, and not those of Maidstone Borough Council -----Original Message----- From: Dirk Koschuetzki [mailto:dkoschuetzki@gmx.de] Sent: Tuesday, July 04, 2000 6:21 PM To: pgsql-interfaces@postgresql.org Subject: [INTERFACES] Default mode for transaction in postgreSQL and JDBC Hello, I played around with the transaction management in postgreSQL and I found that the JDBC-Driver allways indicates that the transaction isolation level is "serializable". This is hard coded within the source and changing the transaction isolation level with the provided method gives an exception. So far so good. A second look in the postgreSQL source code (V 6.5.3) indicates that the default isolation level is read commited, the documentation states the same and a check with psql confirms this. So, is the transaction isolation level within my (6.5.3) JDBC-Version really serializable? Regards Dirk Ps.: Please CC me, as I'm currently not subscribed to the list. -- Dirk Koschützki dkoschuetzki@medialift.com OpenPGP messages welcome Fingerprint: E0C4 74F1 9E21 8C90 EEA7 A65A 1868 A81D 5622 74C4
В списке pgsql-interfaces по дате отправления: