The hard part is to do it portably.
I use a multicast socket that writes the change-event. Then I use a
select() call on the multicast socket in other clients- if they see the
change event, they incorporate the new data into their cache.
If you want it reasonably seamless, create triggers that ev
Hello,
On 10 may 2004, at 12:47, D. Richard Hipp wrote:
The tricky part is knowing when any change has occurred
to the database at all. If you have a single process
that is doing all the changes, then this is simple.
Just build a wrapper around your SQLite access routines
that sends a signal aft
Chris Waters wrote:
[...] I need to know if:
* A row was inserted.
* A row was deleted.
* A row was modified.
I do this by creating three triggers on each table I
want to monitor - one each of DELETE, INSERT, and
UPDATE triggers. Each trigger writes information I
need to know about the operation
On Sun, 9 May 2004, Raymond Irving wrote:
>
>How about being able to add a trigger to the Database?
>
>CREATE TRIGGER db_inserts INSERT ON
>DATABASE|{database_name}
>BEGIN
>
>END
You'd want seperate update, create and insert triggers, as I believe you
can only trigger on a table/view, not a
How about being able to add a trigger to the Database?
CREATE TRIGGER db_inserts INSERT ON
DATABASE|{database_name}
BEGIN
END
--- Chris Waters <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I need the ability to tell if changes have been made
> in the database. Kind
> of like the LISTEN capability
Hi,
I need the ability to tell if changes have been made in the database. Kind
of like the LISTEN capability in Postgresql. In particular I need to know
if:
* A row was inserted.
* A row was deleted.
* A row was modified.
I would like to implement this through a callback that an application coul
6 matches
Mail list logo
