Skip site navigation (1) Skip section navigation (2)

Re: ERROR transaction is read-only

From: interz12(at)yahoo(dot)com
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: ERROR transaction is read-only
Date: 2007-10-24 18:22:59
Message-ID: 321385.55928.qm@web36615.mail.mud.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
FYI, the connection is non-readonly when I initially create it. After
 doing a select, it becomes read-only and I have to manually set it back
 to non-readonly. Is this normal???

----- Original Message ----
From: ahnf <interz12(at)yahoo(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Sent: Wednesday, October 24, 2007 9:17:34 AM
Subject: [JDBC] ERROR transaction is read-only



I am using the postgresql-8.2.506.jdbc4.jar file 

My jdbc connections are setReadOnly(false)

When attempting an insert I get 

org.postgresql.util.PSQLException: ERROR: transaction is read-only

ideas?


org.postgresql.util.PSQLException: ERROR: transaction is read-only
    at
 org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1548)
    at
 org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1316)
    at
 org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
    at
 org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
    at
 org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:351)
    at
 org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:344)



---------------------------(end of
 broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match




pgsql-jdbc by date

Next:From: Matthew StorerDate: 2007-10-24 19:29:14
Subject: Re: "Something unusual has occured" error using PostgreSQL 8.2 with Apache Commons DBCP 1.2.2
Previous:From: ahnfDate: 2007-10-24 15:17:34
Subject: ERROR transaction is read-only

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group