Re: [sqlite] Hung query question

2016-11-18 Thread Eduardo Morras
On Fri, 18 Nov 2016 19:20:06 + David Raymond wrote: > I've got a query that I've tried a few times here that seems like > it's hanging up on something and I'm wondering if it's just some > brain dead thing I'm forgetting or doing wrong. > > I've got a database with

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread Roger Binns
On 17/11/16 19:14, Kevin O'Gorman wrote: > SO: I need help bifurcating this problem. For instance, how can I tell if > the fault lies in SQLite, or in python? Or even in the hardware, given that > the time to failure is so variable? Are you using threads, threading related settings etc in any

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread Kevin O'Gorman
On Fri, Nov 18, 2016 at 8:38 AM, Roger Binns wrote: > On 17/11/16 19:14, Kevin O'Gorman wrote: > > SO: I need help bifurcating this problem. For instance, how can I tell > if > > the fault lies in SQLite, or in python? Or even in the hardware, given > that > > the time to

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread Kevin O'Gorman
On Fri, Nov 18, 2016 at 3:11 AM, Simon Slavin wrote: > Forgot to say ... > > Most of these problems result from attempting to reuse memory you've > already released. Even if the error is happening inside a SQLite routine, > it will be because you passed it a pointer to an

Re: [sqlite] Changing ID's to UUID

2016-11-18 Thread Jens Alfke
> On Nov 16, 2016, at 5:59 AM, Keith Medcalf wrote: > > What I do not understand is why one would use a UUID (randomly generated > bunch of bytes) as a key in a database. It is long, every use must be > checked for collisions, and inherently far less efficient than the

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread Simon Slavin
On 18 Nov 2016, at 6:18pm, James K. Lowden wrote: > The most likely culprit in my mind is RAM. You're exercising new memory > pretty hard, running a bunch of processes at it at full tilt. Any > defect in the chips or DMA could explain what you're seeing. An easy >

Re: [sqlite] Hung query question

2016-11-18 Thread Simon Slavin
On 18 Nov 2016, at 7:20pm, David Raymond wrote: > insert into coordExtremes select State, min(Latitude), max(Latitude), > min(Longitude), max(Longitude) from foo.bar group by State; Apologies. Correction to my earlier post: Create indexes on table foo for the

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread Roger Binns
On 18/11/16 08:55, Kevin O'Gorman wrote: >> I am not. All of the python code is a single thread. The closest I come > is a few times where I use subprocess.Popen to create what amounts to a > pipeline, and one place where I start a number of copies of a C program in > parallel, but each is a

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread James K. Lowden
On Fri, 18 Nov 2016 08:55:11 -0800 "Kevin O'Gorman" wrote: > All of the python code is a single thread. The closest I come > is a few times where I use subprocess.Popen to create what amounts to > a pipeline, and one place where I start a number of copies of a C >

[sqlite] Hung query question

2016-11-18 Thread David Raymond
I've got a query that I've tried a few times here that seems like it's hanging up on something and I'm wondering if it's just some brain dead thing I'm forgetting or doing wrong. I've got a database with a bunch of records, and am trying to populate a table in another database with coordinate

Re: [sqlite] Hung query question

2016-11-18 Thread Simon Slavin
On 18 Nov 2016, at 7:20pm, David Raymond wrote: > insert into coordExtremes select State, min(Latitude), max(Latitude), > min(Longitude), max(Longitude) from foo.bar group by State; Create indexes on table foo for the latitude and longitude columns. CREATE INDEX

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread James K. Lowden
On Fri, 18 Nov 2016 10:56:37 -0800 Roger Binns wrote: > Popen calls fork (it seems like you are doing Unix/Mac, not Windows). > fork() duplicates the process including all open file descriptors. > One or more of those descriptors belong to open SQLite databases and >

Re: [sqlite] Changing ID's to UUID

2016-11-18 Thread James K. Lowden
On Fri, 18 Nov 2016 10:22:15 -0800 Jens Alfke wrote: > You?d have to assign a central ?count server? to hand out consecutive > numbers No. You need only enumerate the sources, and accept that the key is the unique counter from the source plus the centrally assigned source

Re: [sqlite] Anybody know why mono SQLite uses SqliteConnection but Windows uses SQLiteConnection?

2016-11-18 Thread J Decker
mono install.exe often works. On Fri, Nov 18, 2016 at 9:16 PM, Jim Henderson wrote: > Thanks for the suggestion, Bill. > > Will this run on a Linux system? The zip file has Install.exe and Test.exe > inside it. > > Jim > > > On 18-Nov-2016 7:44 AM, Drago, William @

Re: [sqlite] Anybody know why mono SQLite uses SqliteConnection but Windows uses SQLiteConnection?

2016-11-18 Thread Jim Henderson
Thanks for the suggestion, Bill. Will this run on a Linux system? The zip file has Install.exe and Test.exe inside it. Jim On 18-Nov-2016 7:44 AM, Drago, William @ CSG - NARDA-MITEQ wrote: Do any of you know why the two different versions of SQLite have different case in the method names?

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread Simon Slavin
On 18 Nov 2016, at 3:14am, Kevin O'Gorman wrote: > SO: I need help bifurcating this problem. For instance, how can I tell if > the fault lies in SQLite, or in python? Or even in the hardware, given that > the time to failure is so variable? Normal recommendation is to

Re: [sqlite] I keep getting seg faults building my database using python sqlite3

2016-11-18 Thread Simon Slavin
Forgot to say ... Most of these problems result from attempting to reuse memory you've already released. Even if the error is happening inside a SQLite routine, it will be because you passed it a pointer to an SQLite connection which had already been _close()'d or a statement which had