Skip to content
Back to formatted view

Raw Message

Message-ID: <m2zlustorw.fsf@userprimary.net>
Date: 2008-01-26T18:39:15Z
From: Seth Falcon
Subject: RSQLite: ATTACH statement not executed when the db connection is holding a resultSet
In-Reply-To: <m2lk6ld5tq.fsf@userprimary.net> (Seth Falcon's message of "Sat\, 19 Jan 2008 10\:32\:33 -0800")

Hi all,

Seth Falcon <seth at userprimary.net> writes:
> I think there are two ways to go here:
>
> 1. Fix dbGetQuery to have the same auto-close semantics.
>
> 2. Remove the auto-close feature entirely.  Should dbGetQuery change
>    too such that it fails when a ResultSet is open instead of opening
>    a new connection?  That is easier to explain, but not at all
>    backwards compatible.

I've just uploaded a new RSQLite 0.6-7 with the following changes:

* dbGetQuery now has the same auto-close semantics as dbSendQuery

* dbGetQuery issues a warning message when it opens a temporary
  connection because there is an incomplete result set.

+ seth

-- 
Seth Falcon | seth at userprimary.net | blog: http://userprimary.net/user/