Re: sqlLite

by updated info i assumed you meant notifications? (i.e. one client gets a
bleep when another updates a new table). doing that really dynamically
(i.e. tell me when "SELECT X FROM Y changes results") would be hard, also
"tell me when TABLE X has changed" might cause problems with lots of
updates (assuming the primary function was to update GUIs that is)
It should be relatively easy to add meta-data to the tables to give you an
mtime which you could then query at your lesure: i,e "SELECT _mtime from
X" or something which you could poll....

hmm polling is annoying though...

With an active callback the client is basically going to want to re-query
its data, which might lead to problems or it might not.....

on second thoughts if you only notify after an insert/update transaction
and you beat anybody about the head who doesn't group their writing
transactions it should be fairly neat.

I will think about it.

owen

On 11 Feb 2002, Robert Mibus wrote:

> On Sun, 2002-02-10 at 13:43, Owen Cliffe wrote:
> > Just out of curiosity is anybody else hacking a networked lightweight
> > sqld?
> >
> > I have started working on a really basic sqlite-based sql daemon, which
> > while not giving you a huge advantage over basic libsqlite should be a
> > start.
> What sort of changes have you made? Ones that send IPC messages for
> updated info, etc?
>
> Thanks;
> mibus
>
>

-- 
Owen Cliffe, Ph.D. Student, Dept. Computer Science
University of Bath