[sqlite] 2nd Call For Papers - 24th Annual Tcl/Tk Conference (Tcl'2017)

Hello SQLite Users, fyi ... 24th Annual Tcl/Tk Conference (Tcl'2017) http://www.tcl.tk/community/tcl2017/ October 16 - 20, 2017 Crowne Plaza Houston River Oaks 2712 Southwest Freeway, 77098 Houston, Texas, USA Important Dates: Abstracts and proposals due August 21, 2017 Notification to

Re: [sqlite] SELECT INTO TEMP TABLE takes long

Thanks guys for all the information. Now I know, how to proceed. Tom :) Am 31.05.2017 um 22:02 schrieb R Smith: On 2017/05/31 9:31 PM, Thomas Flemming wrote: Hi, maybe, hopefully, I missed something, its still about this database: http://files.qvgps.com/0-tom-public/Geonames_World_2017.zip

Re: [sqlite] SELECT INTO TEMP TABLE takes long

On 2017/05/31 9:31 PM, Thomas Flemming wrote: Hi, maybe, hopefully, I missed something, its still about this database: http://files.qvgps.com/0-tom-public/Geonames_World_2017.zip Copying just the ids from 12mio records ordered in a temp-table takes 60 seconds. There is a COLLATE NOCASE

Re: [sqlite] Segfaults from lemon program

On 5/31/17, Ryan Whitworth wrote: > > I was using American Fuzzy Lop on the lemon program included with sqlite3 > and found inputs that cause segmentation faults. Are these sort of errors > something to report to this list? > Suppose we spent time and fixed this segfault

Re: [sqlite] SELECT INTO TEMP TABLE takes long

On 31 May 2017, at 8:31pm, Thomas Flemming wrote: > Copying just the ids from 12mio records ordered in a temp-table takes 60 > seconds. There is a COLLATE NOCASE index on label. > > Is this normal or can this also be done faster? > > DROP TABLE IF EXISTS RowCursor; > CREATE

[sqlite] Segfaults from lemon program

Hello, I was using American Fuzzy Lop on the lemon program included with sqlite3 and found inputs that cause segmentation faults. Are these sort of errors something to report to this list? Thanks, Ryan Whitworth m...@ryanwhitworth.com ___ sqlite-users

[sqlite] SELECT INTO TEMP TABLE takes long

Hi, maybe, hopefully, I missed something, its still about this database: http://files.qvgps.com/0-tom-public/Geonames_World_2017.zip Copying just the ids from 12mio records ordered in a temp-table takes 60 seconds. There is a COLLATE NOCASE index on label. Is this normal or can this also be

Re: [sqlite] Android App crash

On 30 May 2017, at 7:10pm, Salih Erikci wrote: > I am getting an error in my android app Sorry, but without some sort of error message or result code we can’t guess what’s wrong. Since you’re getting your backtrace from Google Play you might be able to get help from

Re: [sqlite] Sqlite 3 own function integration in c

On 30 May 2017, at 6:30pm, t682993 wrote: > I am testing sqlite and find it very versatile and good. > I am just missing 1 thing: from a table column i would like that the > sql-engine could generate new UUID or GUID per row. format >

[sqlite] Android App crash

Hi, I am getting an error in my android app, and it looks like sqlite related but i can't figure out what the problem is.I am using the 2 lower() functions in a select statement. This is the backtrace Google Play gives me. backtrace: native: pc 0005906c /system/lib/libicuuc.so native: pc

[sqlite] Sqlite 3 own function integration in c

Hello guys, Operating system: Mac OSX El Capitan 10.11.6 Product: sqlite - dbrowser 3 I am testing sqlite and find it very versatile and good. I am just missing 1 thing: from a table column i would like that the sql-engine could generate new UUID or GUID per row. format

Re: [sqlite] Importing from single-insert-statement SQL dump is 61 times slower than importing from SQL dump with one statement per row

Looking at the generated program for mulit-tuple INSERT INTO ... VALUE yields the following structure: Only 1 tuple (standard case) 2 tuples Each further tuple adds a segment (1 opcode per field + data) and a yield opcode to the generated VDBE program, and an equivalent amount