With great trepidation I announce the 0.1 version of the swiplite pack (add-on). It is not ready but it can already be used; or at least looked at. The code is available at GitHub - borisvassilev/swiplite: SQLite for SWI-Prolog . You should be able to clone it and see what is in there. I have tried…

[image] Boris: was such a binding really necessary? You make that hard to judge as you do not say what motivated you to create it :slight_smile: Just bundling sqlite should not be enough. You could simply have created a package derived from "prosqlite" pack for SWI-Prolog . You can also us…

[image] Boris: Any feedback is greatly appreciated. My meta-comment is: why did you decide to use C instead of C++ ? The latter should be both easier to use and less error-prone (e.g., handling errors and cleanup) than the C interface; there is a small performance hit but I think it’s unlikely…

[image] jan: You make that hard to judge as you do not say what motivated you to create it :slight_smile: Just bundling sqlite should not be enough. You could simply have created a package derived from "prosqlite" pack for SWI-Prolog . I didn’t want to influence anyone’s judgement by selling i…

Because I don’t know how to program, esp in C++. Learning C++ might be my next hobby project.

[image] Boris: Because I don’t know how to program, esp in C++ You can mostly use C++ as a “better C than C”. And I’ve tried to document the trickier uses of “smart pointers” and RAII – if the documentation isn’t good enough, please send me feedback! BTW, as you’re “learning” … what developm…

[image] peter.ludemann: BTW, as you’re “learning” … what development environment and platform are you using? I use a text editor? I have a Linux and a Mac OS and have tried to test both with this particular pack.

[image] jan: Just bundling sqlite should not be enough. If you mean this “amalgamation” thing, I guess I just like the sound of it. There is no reason to use it on any Linux or Mac OS, since both have SQLite installed, and if not, it can be obtained from a package manager. I added the option …

I now added proper installation instructions and some background on why this work was necessary in the README .

This interface makes sense to me. I do miss an sqlite_eval(++Statement, -Row) as nondet predicate. That allows for a comfortable definition of a normal Prolog predicate based on an SQL query, as well as providing comfortable access to too many rows to fit in memory. You can build that on top …

Thank you for the feedback. I specifically defined sqlite_eval/4 as it is now because I thought this can be used with lazy_list/2 , in order to be able to then use member/2 on that list to get the backtracking semidet predicate you descibe. I will revisit this for certain since this was the intent an…

Yet another SQLite binding for SWI-Prolog

Announce Pack

Topic		Replies	Views
A thin Prolog wrapper for SQLite Pack	4	107	April 26, 2026
Pack Ann: proSQLite 2.0 Pack	0	77	August 15, 2024
SQLite dependency in a pack Pack discussion	12	230	July 31, 2024
Building prosqlite from source ? (with a view towards osquery) General	1	141	June 2, 2024
Pack Ann: Real + proSQLite --- for SWI 8.2.0 Pack	0	1900	May 29, 2020

Yet another SQLite binding for SWI-Prolog

Related topics