On Fri, Sep 13, 2019 at 6:38 PM Jens Alfke wrote:
> (b) Execute "SELECT key, … FROM table WHERE key IN (…)", including all of
> the key strings.
>
> If I do (b), SQLite has less setup work to do, and it could potentially
> optimize the b-tree lookup. On the downside, I have to prepare a
> On Sep 17, 2019, at 8:13 AM, Peng Yu wrote:
>
> I can compile it. Where do I put the .dylib file?
According to the documentation Warren linked to, you use a SQL statement or
shell dot-command to load the extension, giving the path to the library.
—Jens
>I edited this second script to use plain apsw.
>In the vi editor:
>%s/db.execute/db.cursor().execute/
>%s/executescript/execute/
>%s/db.commit()/db.cursor().execute("COMMIT")/
>/Method 9
>.,$d
>
>(the carray tests are left out)
>My test output for 1000 keys is:
>$ python3 keith2b.py 1000
gcc -g -fPIC -dynamiclib regexp.c -o regexp.dylib
I can compile it. Where do I put the .dylib file?
$ cat /usr/local/opt/sqlite/lib/pkgconfig/sqlite3.pc
# Package Information for pkg-config
prefix=/usr/local/Cellar/sqlite/3.29.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
>
> Op 17 sep. 2019, om 04:26 heeft Keith Medcalf het
> volgende geschreven:
>
>
> On Monday, 16 September, 2019 14:22, E.Pasma wrote:
>
>> Stop stop stop
>
> You are right. What a difference a spelling error makes ... No wonder it
> took so long as it was doing table scans -- and the
5 matches
Mail list logo