Re: sqlLite

On Mon, 2002-02-11 at 14:52, Owen Cliffe wrote:
> 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
Yes.

> (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....
Maybe...

> hmm polling is annoying though...
And the "wrong" thing to do IMO.

> 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.
Sounds good. IIRC evolution actually uses the 'notification' system to
populate the UI the first time. Basically, the app provides a callback
for 'update_card' and 'add_card' (for instance) and calls 'open_book',
which then sends n events to add_card or update_card. (IIRC :)

> I will think about it.
Great. It'd be nice to do it; if it could handle that, delete/etc *and*
have an mtime then syncing is already half-completed :-)

> owen
mibus

-- 
Robert Mibus <mibus@bigpond.com>
Civilization, as we know it, will end sometime this evening.
Full story tomorrow.