On Saturday 17 March 2007 13:51, John Nagle wrote:
> jim-on-linux wrote:
> > On Friday 16 March 2007 18:23, Jerry Hill
wrote:
> >>On 3/16/07, jim-on-linux
> >> <[EMAIL PROTECTED]>
> >
> > wrote:
> >>>Below, the first select produces results
> >>> but, after closing then re-opening the
> >>> databa
jim-on-linux wrote:
> On Friday 16 March 2007 18:23, Jerry Hill wrote:
>
>>On 3/16/07, jim-on-linux <[EMAIL PROTECTED]>
>
> wrote:
>
>>>Below, the first select produces results but,
>>>after closing then re-opening the database
>>>the select produces an empty list. Anyone
>>>know the reason ??
On Friday 16 March 2007 18:23, Jerry Hill wrote:
> On 3/16/07, jim-on-linux <[EMAIL PROTECTED]>
wrote:
> > Below, the first select produces results but,
> > after closing then re-opening the database
> > the select produces an empty list. Anyone
> > know the reason ??
>
> When you first open a co
On 3/16/07, jim-on-linux <[EMAIL PROTECTED]> wrote:
> Below, the first select produces results but,
> after closing then re-opening the database the
> select produces an empty list. Anyone know the
> reason ??
When you first open a connection, you implicitly begin a transaction.
You need to call
from John Clark
use con.commit()
Thanks John,
this works
jim-on-linux
On Friday 16 March 2007 17:55, jim-on-linux wrote:
> Python help,
>
> I just started working with SQLite3 and ran
> into this problem.
>
> Below, the first select produces results but,
> after closing then re-opening the
Python help,
I just started working with SQLite3 and ran into
this problem.
Below, the first select produces results but,
after closing then re-opening the database the
select produces an empty list. Anyone know the
reason ??
The table seems to be empty.
import sqlite3
con = sqlite3.c
