Thanks, Igor! You're awesome...
Igor Tandetnik wrote:
>
> Simon Chen wrote:
>> I just realized that I need to something a bit more complicated.
>> Basically, I need myfunction() to take parameters. The parameters
>> should be generated based on the entry inserted, like something below:
>>
>> c
Simon Chen wrote:
> I just realized that I need to something a bit more complicated.
> Basically, I need myfunction() to take parameters. The parameters
> should be generated based on the entry inserted, like something below:
>
> create trigger triggerName before insert on tableName1
> when not m
lite.org
Subject: Re: [sqlite] how to call c/c++ function in trigger
I just realized that I need to something a bit more complicated. Basically,
I
need myfunction() to take parameters. The parameters should be generated
based on the entry inserted, like something below:
create trigger triggerN
I just realized that I need to something a bit more complicated. Basically, I
need myfunction() to take parameters. The parameters should be generated
based on the entry inserted, like something below:
create trigger triggerName before insert on tableName1
when not myfunction(tableName1.name, t
Simon Chen wrote:
> Another question is, if the c/c++ function takes 10 seconds to
> finish, when another process queries the exact entry being modified,
> what will be returned?
Either the old data, or the busy error - depending on whether your
writing connection had to spill from in-memory cac
Another question is, if the c/c++ function takes 10 seconds to finish, when
another process queries the exact entry being modified, what will be
returned? Maybe the old data? Is it possible to lock this entry so that
either the new value (when check passes) or old value (when check fails)
will be
Thank you very much!
Igor Tandetnik wrote:
>
> Simon Chen wrote:
>> What I want is:
>>
>> - whenever I insert/update/delete a table entry, the specified c/c++
>> function is called
>> - if the function returns true, the db action can proceed; otherwise,
>> the db action should be rolled-back.
Simon Chen wrote:
> What I want is:
>
> - whenever I insert/update/delete a table entry, the specified c/c++
> function is called
> - if the function returns true, the db action can proceed; otherwise,
> the db action should be rolled-back.
create trigger triggerName before insert on tableName
8 matches
Mail list logo