Isn't it easier to just call: sqlite3_last_insert_rowid()?
Olaf
- Original Message -
From: "Jay Sprenkle" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Monday, July 24, 2006 5:17 PM
Subject: Re: [sqlite] Getting callback with an INSERT
> On 7/2
> -Original Message-
> From: John Stanton [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 24, 2006 2:14 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Getting callback with an INSERT
>
> Olaf Beckman Lapré wrote:
> > No, that's not the case since
onday, July 24, 2006 5:30 PM
Subject: Re: [sqlite] Getting callback with an INSERT
It hardly seems necessary to make it a callback since you could just
call your function concurrently with the INSERT SQL.
Olaf Beckman Lapré wrote:
Is it possible to get a callback when doing an INSERT on a table
M
Subject: Re: [sqlite] Getting callback with an INSERT
> It hardly seems necessary to make it a callback since you could just
> call your function concurrently with the INSERT SQL.
>
> Olaf Beckman Lapré wrote:
> > Is it possible to get a callback when doing an INSERT on a table si
It hardly seems necessary to make it a callback since you could just
call your function concurrently with the INSERT SQL.
Olaf Beckman Lapré wrote:
Is it possible to get a callback when doing an INSERT on a table similar to a SELECT callback? The callback would then contain the same parameters
On 7/24/06, Dennis Cote <[EMAIL PROTECTED]> wrote:
You can do this by adding an insert trigger to your table and
registering a user function that will call back to your code.
create trigger t_in after insert on t
begin
select do_insert_callback(new.rowid);
end;
You will have to
Olaf Beckman Lapré wrote:
Is it possible to get a callback when doing an INSERT on a table similar to a SELECT callback? The callback would then contain the same parameters but only contain the row(s) being inserted.
The reason I'm asking is that this may be usefull in GUI applications where
7 matches
Mail list logo
