Re: [pysqlite] Seg Fault Only When Table Contains Data

 -------------- Original message ----------------------
From: Rich Shepard <[email protected]>
> On Tue, 3 Jun 2008, Adrian Klaver wrote:
> 
> > Thought the problem might be the cursor was selecting too much data for
> > the memory available. In your previous message the onSave() function
> > showed a query with 33 columns, are we talking about the same thing?
> 
> Adrian,
> 
>    Yes.
> 
>    However, if I manually enter data into a single row and two columns, the
> app still seg faults when I try to load it again.
> 
> > Without seeing more of the code I am at a loss for an explanation.
> 
>    Well, none of this makes any sense to me. I've attached the entire module,
> dataPage.py. No matter what I try, I cannot isolate the problem. FWIW,
> here's the scheme for the Data table:
> 
> CREATE TABLE Data (comp TEXT NOT NULL, subcomp TEXT, var TEXT NOT NULL,
> curr1 TEXT, curr2 TEXT, curr3 TEXT, curr4 TEXT, curr5 TEXT, curr6 TEXT, 
> curr7 TEXT, curr8 TEXT, curr9 TEXT, curr10 TEXT, curr11 TEXT, curr12 TEXT,
> noact TEXT, alt2 TEXT, alt3 TEXT, alt4 TEXT, alt5 TEXT, alt6 TEXT, alt7
> TEXT, alt8 TEXT, alt9 TEXT, alt10 TEXT, alt11 TEXT, alt12 TEXT, alt13 TEXT, 
> alt14 TEXT, alt15 TEXT, alt16 TEXT, alt17 TEXT, alt18 TEXT,
> PRIMARY KEY (comp, subcomp, var));
> 
> Rich
> 

A couple of things:
self.nRows = self.GetNumberRows()  I know this is overriding self.dataGrid.GetNumberRows() but I would rename it just to avoid potential naming issues.

where does:
self.appData.cur.execute("SELECT * from Data") occur?


 

--
Adrian Klaver
[email protected]

_______________________________________________
list-pysqlite mailing list
list-pysqlite-FR6EJeJVuqdwc357pe9rcyQmJico6nz3epZhswDD4dQ@public.gmane.org
http://itsystementwicklung.de/cgi-bin/mailman/listinfo/list-pysqlite