Another exception (Transaction level)

Поиск
Список
Период
Сортировка
Искать
От
Ole Streicher
Тема
Another exception (Transaction level)
Дата
Msg-id
qfd6fyx0xh.fsf@ebp00439.ebp.de
Список
Дерево обсуждения
Another exception (Transaction level) Ole Streicher <ole-usenet-spam@gmx.net>
Re: Another exception (Transaction level) Paul Thomas <paul@tmsl.demon.co.uk>
Re: Another exception (Transaction level) Ole Streicher <ole-usenet-spam@gmx.net>
Re: Another exception (Transaction level) Paul Thomas <paul@tmsl.demon.co.uk>
Re: Another exception (Transaction level) Ole Streicher <ole-usenet-spam@gmx.net>
Re: Another exception (Transaction level) Csaba Nagy <nagy@ecircle-ag.com>
Re: Another exception (Transaction level) Paul Thomas <paul@tmsl.demon.co.uk>
Re: Another exception (Transaction level) Ole Streicher <ole-usenet-spam@gmx.net>
Hi,

sorry if I flood you with lots of messages, but I am quite new to
Postgresql and I find a lot of questions not answered in the manual.

I get randomly (probably when I have concurrent r/w access) the error
message

java.sql.SQLException: ERROR:  SET TRANSACTION ISOLATION LEVEL must be called before any query

when I do a commit(). But I had set this level at the very beginning with

dbConn.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED);

BTW, I tried to use TRANSACTION_READ_UNCOMMITTED (which is described
in the manual) but in this case I get "Transaction isolation level 1
is not supported."

What is wrong here? Why do I get an error message when I try to use
the "read uncommitted" level, and why I get the exception when I use
commit() after setting the transaction level to "read committed"?

Ciao

Ole
В списке pgsql-jdbc по дате отправления
От: Ole Streicher
Дата:
От: Felipe Schnack
Дата:
FAQ