RE: Connection.setBytes()
От | Peter Mount |
---|---|
Тема | RE: Connection.setBytes() |
Дата | |
Msg-id | 1B3D5E532D18D311861A00600865478CF1B0F3@exchange1.nt.maidstone.gov.uk обсуждение исходный текст |
Ответ на | Connection.setBytes() (Matt Fair <matt@netasol.com>) |
Список | pgsql-interfaces |
The best point is just after you get a Connection object. ie: conn.setAutoCommit(false); Then when you issue any updates, you need to call conn.commit(); to commit the changes to the database. Peter -- Peter Mount Enterprise Support Maidstone Borough Council Any views stated are my own, and not those of Maidstone Borough Council -----Original Message----- From: ChristophSchmidt [mailto:cs.hilzingen@swol.de] Sent: Tuesday, July 18, 2000 8:33 PM To: Joachim Achtzehnter; pgsql-interfaces@postgresql.org Subject: Re: [INTERFACES] Connection.setBytes() Am Die, 18 Jul 2000 schrieben Sie: > On Tue, 18 Jul 2000, Matt Fair wrote: > > > > I want to set an array of bytes to a prepared statement, but it throws a > > null pointer exception. > > Did you turn off autocommit? BLOB code must run in the context of a > transaction. I believe autocommit defaults to true, so you must explicitly > set it to false and call commit at the end of your transactions. > > Joachim Hi, where is the point to turn autocommit off ? (how do you turn it off ) I am new to PREPARED STATEMENT... Where can i find the documentation ? How much more efficient is it ? Is it similar to stored procedures/functions ? cs
В списке pgsql-interfaces по дате отправления: