Re: Disappearing Data

On Tue, 28 Nov 2006, Adrian Klaver wrote:

> Generally this indicates that a con.commit() has not been issued. The data
> was written in the session but rolled back when the session was left
> without issuing a commit(). See section 5 of the usage guide. In
> particular the part about setting isolation level to None. This sets the
> connection to autocommit.

   Well, I couldn't wait. :-) By putting 'self.appData.con.commit()'
immediately after the call to DBtools().SaveDB() -- and fixing the multiple
connection/cursor situation in that file -- it all works now!

sqlite> select * from model;
foobar|some text|Fuzzy reasoning|name me|-1

   Thank you all. I learned quite a bit today even it it took all day to get
these few functions working.

   So, tomorrow is fixing all the calls to the database in all modules and
continue testing.

Rich

-- 
Richard B. Shepard, Ph.D.               |    The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)    |            Accelerator
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863