Re: [pysqlite] Seg Fault Only When Table Contains Data
[email protected] (Adrian Klaver) Tue, 03 Jun 2008 19:38:17 +0000
| Newsgroups | gmane.comp.python.db.pysqlite.user |
|---|---|
| Message-ID | <060320081938.3533.48459DA9000AFA8200000DCD22058891169D0A900E04050E@comcast.net> |
-------------- Original message ---------------------- From: Rich Shepard <[email protected]> > On Mon, 2 Jun 2008, Adrian Klaver wrote: > > > Something about the data is causing the problem, either a data type mismatch > > or too much data. > > Adrian, > > What do you mean by "too much data?" There are three columns of strings > (some have the second column empty), and 114 rows. > 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? > > Might try: self.appData.cur.execute("SELECT * from Data limit 10") to see > > if its a excess data problem. > > Makes no difference. The limit can be 10, 5, or 1 and it still seg faults > when I try invoking the app. > > > Try the following to see if its an empty string problem: > > for c in range(33): > > if self.dataGrid.GetCellValue(r,c) == None: > > row.append('None) > > I did this without the initial single quote. No difference! > > This is completely strange and highly puzzling. There are no issues when I > look at the data with the SQLite shell. There are also no issues when data > are presented in any other widget type. This issue is really hanging me up > in a serious way. Without seeing more of the code I am at a loss for an explanation. > > Rich > -- Adrian Klaver [email protected] _______________________________________________ list-pysqlite mailing list list-pysqlite-FR6EJeJVuqdwc357pe9rcyQmJico6nz3epZhswDD4dQ@public.gmane.org http://itsystementwicklung.de/cgi-bin/mailman/listinfo/list-pysqlite
(unnamed)
(message/rfc822, 807 B) - not displayed