Would it be very challenging to tweak the SQLite/Tcl code such that
something like this (below) would work?
---
#!/usr/bin/env tclsh8.6
package require sqlite3
sqlite3 db "test.db"
db eval { CREATE TABLE ex_table (
ex_id INTEGER NOT NULL,
On 08/26/2016 01:20 PM, David Raymond wrote:
[snip]
> Many do not persist after closing your connection, including synchronous and
> foreign_keys that you mentioned. In fact, I'd say that the number that do
> persist is pretty small, and those that do usually require a vacuum or such
> after
On 08/25/2016 04:41 PM, Adam Jensen wrote:
> On 08/20/2016 01:01 PM, Simon Slavin wrote:
>> On 20 Aug 2016, at 5:56pm, Lev <leventel...@gmail.com> wrote:
> [snip]
>>> So this 'setting' is stored in the database file? Is it enough to do the
>>> PRAGMA when the da
On 08/20/2016 01:01 PM, Simon Slavin wrote:
> On 20 Aug 2016, at 5:56pm, Lev wrote:
[snip]
>> So this 'setting' is stored in the database file? Is it enough to do the
>> PRAGMA when the database is created?
>
> Yes and yes, but do it this way.
>
> 1) Create the database
Hello,
I am interested in exploring the capabilities of [The Session
Extension](http://www.sqlite.org/sessionintro.html). The documentation
is currently a bit weak. Does anyone have any examples of how this
extension might be used from the sqlite3 application or a Tcl interface?
Thanks!
5 matches
Mail list logo