The 3.20.0 release will be delayed. Some concerns came up over the
new sqlite3_value_pointer() interface. Interface chagnes were made
over the weekend. But there are still concerns. So the decision has
been made to back off and give the current design a few weeks to soak
before trying to press
On Mon, Jul 17, 2017 at 5:43 PM, petern wrote:
> Speaking of type string lifetime, what about pointer lifetime management?
>
> I think you've overlooked the pointer lifetime problem for
> sqlite3_result_pointer(C,P,T). This form, unlike the blob form, lacks the
>
This seems to be exactly what I'm looking for. Thanks!
--Ron
Op ma 17 jul. 2017 om 20:23 schreef Jens Alfke
>
> > On Jul 17, 2017, at 11:08 AM, Ron wrote:
> >
> > I am looking into the possibility of putting the changes in SQLite
> database
> > into
> On Jul 17, 2017, at 11:08 AM, Ron wrote:
>
> I am looking into the possibility of putting the changes in SQLite database
> into kafka, similar to this:
> https://www.confluent.io/blog/bottled-water-real-time-integration-of-postgresql-and-kafka/
>
>
First, apologies for sending without a subject line, pressed send too soon.
I would need all changes in all tables, but not transactions that did not
execute. How would I fill about setting this up?
Op ma 17 jul. 2017 om 20:14 schreef Jay Kreibich
>
> I’d look at creating a
I’d look at creating a virtual table that can be setup to “shadow” any existing
table. Basically pass-through any read or write operations, possibly shunting
off writes. This has the advantage of not requiring any kind of patching or
modifications to the core library. Sounds a lot simpler
Hi,
Before I dive into the SQLite internals, I'd like to ask the mailing list
first.
I am looking into the possibility of putting the changes in SQLite database
into kafka, similar to this:
https://www.confluent.io/blog/bottled-water-real-time-integration-of-postgresql-and-kafka/
.
Would it be
I'm trying to write up a document on the whole sqlite3_bind_pointer()
thing now, that describes its motivation and its limitations.
Hopefully that will clear up the confusion. I will announce when the
new document goes up and request clearance from petern and kmedcalf
prior to the release.
On
On Monday, 17 July, 2017 08:00, Richard Hipp wrote:
> On 7/17/17, Keith Medcalf wrote:
> > Also, a question. sqlite3_bind_pointer(C, P, T) and
> > sqlite3_value_pointer(C, P, T) indicates that T should be a "static
> > string".
> > Does this mean of type
Speaking of type string lifetime, what about pointer lifetime management?
I think you've overlooked the pointer lifetime problem for
sqlite3_result_pointer(C,P,T). This form, unlike the blob form, lacks the
destructor callback for cleanup when SQLite determines the scope of the
last statement
On 7/17/17, Dan Ackroyd wrote:
> Hi Rowan,
>
> Thanks for the feedback. fyi The problem seems to be with the version
> of SQLite shipped with PHP.
>
> Compiling with the version that PHP uses and running a little test, I get:
>
> versionString: "3.15.1"
> Error message:
On 7/17/17, Keith Medcalf wrote:
>
> Also, a question. sqlite3_bind_pointer(C, P, T) and
> sqlite3_value_pointer(C, P, T) indicates that T should be a "static string".
> Does this mean of type SQLITE_STATIC and that it cannot be a string located
> on the stack (ie, an
https://sqlite.org/draft/c3ref/result_blob.html
host-language pointer P or type T
or should be of
Also, a question. sqlite3_bind_pointer(C, P, T) and sqlite3_value_pointer(C,
P, T) indicates that T should be a "static string". Does this mean of type
SQLITE_STATIC and that it cannot be a
Hi Rowan,
Thanks for the feedback. fyi The problem seems to be with the version
of SQLite shipped with PHP.
Compiling with the version that PHP uses and running a little test, I get:
versionString: "3.15.1"
Error message: out of memory
But compiling SQLite from source and then using that gives
On 7/17/17, petern wrote:
> Missing documentation or wrong extension source?
The documentation and code you are looking are from different branches.
>
> https://www.sqlite.org/src/file/ext/misc/remember.c line 51:
> -> ptr = sqlite3_value_pointer(argv[1], "carray");
If runtime disablement of one or more whole triggers is desired, their
execution can be gated by adding a conditioned WHEN clause (or logical
conjuction with existing WHEN clause) to the offending trigger declaration.
https://sqlite.org/syntax/create-trigger-stmt.html
For example:
CREATE
Your https://www.sqlite.org/whentouse.html page uses "emphasis" where it needs
"emphasize".
It's in the second paragraph: "They emphasis scalability...".
Sent from my iPad
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
Thomas Flemming wrote:
> Is there a way in SQLite, to temporary disable and enable a trigger without
> dropping and recreating ?
You could disable recursive triggers, and then make your triggers
recursive by executing all your SQL statements through a temporary
trigger on some temporary table.
18 matches
Mail list logo