If the table doesn't have to be 100% accurate, you could always timestamp
the rows and have connected clients update their row, while old rows get
reaped periodicaly.
On Fri, 7 Nov 2003, Boris Popov wrote:
> I do want them to be visible to everybody. This is a sessions pool,
> where sessions are inserted when our app connects and removed when it
> disconnects, however this would only work for graceful disconnects,
> which we all know isn't always the case. So I want a table that is
> somehow notified of a session disconnect and deletes rows created by
> that session.
>
> Any ideas?