SQLite + JSON support via UDBCSQLite3 in Pharo

Hi all,

I have finished my dummy data mock ups as you can see below (or in [1][2] )

Now I'm ready to start injecting real data into them. Because data comes from a JSON dump, I would like to use the JSON1 extension of SQLite, [3][4], which means compiling it by myself from SQLite amalgamation and putting the binary in a place where UDBCSQLite3 is aware of it. I'm on a Linux 64 bits machine and I have sqlite2 32 bits binary from the distro repositories. When I linked the distro provided binary to the image location, UDBCSQLite3 works fine (but precompiled binary doesn't have JSON1 extension enabled), but when I put there my compiled binary with JSON1 support instead, UDBC complains about "external module not found". How can I made UDBCSQLite3 aware of my compiled binary ?

Thanks,

Offray

Hi,

For the moment it seems that Pharo + SQLite3 + JSON1 will not be needed. NeoJSON is making an excellent work for querying the JSON file. By the way, I was testing with Punqlite and the installation process is very friendly. It even load the unqlite.so and puts it in the proper location (but I'm using NeoJSON just fine).

Cheers,

Offray

Hi all,

I have finished my dummy data mock ups as you can see below (or in [1][2] )

[1] https://www.list.inf.unibe.ch/pipermail/moose-dev/2016-June/025799.html

[2] https://offray.withknown.com/2016/data-selfie-dummy

Now I'm ready to start injecting real data into them. Because data comes from a JSON dump, I would like to use the JSON1 extension of SQLite, [3][4], which means compiling it by myself from SQLite amalgamation and putting the binary in a place where UDBCSQLite3 is aware of it. I'm on a Linux 64 bits machine and I have sqlite2 32 bits binary from the distro repositories. When I linked the distro provided binary to the image location, UDBCSQLite3 works fine (but precompiled binary doesn't have JSON1 extension enabled), but when I put there my compiled binary with JSON1 support instead, UDBC complains about "external module not found". How can I made UDBCSQLite3 aware of my compiled binary ?

[3] https://www.sqlite.org/json1.html

[4] http://www.samadhiweb.com/blog/2016.04.24.sqlite.json.html

Thanks,

Offray

Hi Ben,

Yes I tryed with the -m32 flag and I ldd confirms the use of 32 bit libraries on my system:

ldd sqlite3
        linux-gate.so.1 (0xf7744000)
        libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf76e9000)
        libdl.so.2 => /usr/lib32/libdl.so.2 (0xf76e4000)
        libc.so.6 => /usr/lib32/libc.so.6 (0xf752f000)
        /lib/ld-linux.so.2 (0xf7745000)

Anyway, I'm working with NeoJSON and is working pretty well.

Thanks,

Offray

On Fri, Jul 1, 2016 at 12:49 AM, Offray Vladimir Luna Cárdenas <[hidden email]> wrote:

Hi all,

I have finished my dummy data mock ups as you can see below (or in [1][2] )

[1] https://www.list.inf.unibe.ch/pipermail/moose-dev/2016-June/025799.html

[2] https://offray.withknown.com/2016/data-selfie-dummy

Now I'm ready to start injecting real data into them. Because data comes from a JSON dump, I would like to use the JSON1 extension of SQLite, [3][4], which means compiling it by myself from SQLite amalgamation and putting the binary in a place where UDBCSQLite3 is aware of it. I'm on a Linux 64 bits machine and I have sqlite2 32 bits binary from the distro repositories. When I linked the distro provided binary to the image location, UDBCSQLite3 works fine (but precompiled binary doesn't have JSON1 extension enabled), but when I put there my compiled binary with JSON1 support instead, UDBC complains about "external module not found". How can I made UDBCSQLite3 aware of my compiled binary ?

[3] https://www.sqlite.org/json1.html

[4] http://www.samadhiweb.com/blog/2016.04.24.sqlite.json.html

Thanks,

Offray

Did you do something like...?

http://stackoverflow.com/questions/3501878/force-gcc-to-compile-32-bit-programs-on-64-bit-platform

cheers -ben