Re: [BUGS] BUG #1347: Bulk Import stopps after a while (
От | Kris Jurka |
---|---|
Тема | Re: [BUGS] BUG #1347: Bulk Import stopps after a while ( |
Дата | |
Msg-id | Pine.BSO.4.56.0412221811190.15268@leary.csoft.net обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #1347: Bulk Import stopps after a while ( (Oliver Jowett <oliver@opencloud.com>) |
Ответы |
Re: [BUGS] BUG #1347: Bulk Import stopps after a while (
|
Список | pgsql-jdbc |
On Thu, 23 Dec 2004, Oliver Jowett wrote: > I don't have the code to hand, but from memory an explicit > close of the Query does exactly this -- it clears the > reference which causes it to be immeditately enqueued, and > the next query will do cleanup when it polls the reference > queue. This is true for the Query/Portal objects, the problem is that the Statement/ResultSets aren't closing the underlying objects. Will fix. > I was more worried about why a batch update was generating > so many individual named statements.. it should either use > zero (Statement.addBatch) or one > (PreparedStatement.addBatch) named statement, not N statements. > Ahhh. The protocol is a problem, but this named statement misuse is triggering it. I can take a look at that. Kris Jurka
В списке pgsql-jdbc по дате отправления: