<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.2.3">
</HEAD>
<BODY>
Hi Daniel,<BR>
<BR>
rls_watchers is the same as active_watchers (holding state for presence dialogs). No persistent data is held in these tables.<BR>
<BR>
Hugh (who did the extra headers development) is looking at the silo table.<BR>
<BR>
Regards,<BR>
<BR>
Peter<BR>
<BR>
On Fri, 2012-05-04 at 09:40 +0200, Daniel-Constantin Mierla wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Hello,
looking at changes in the database structure from 3.2 to 3.3, I noticed
the columns in active_watchers/rls_watches that have no default value
and cannot be NULL.
The usual issue with this kind of upgrades is that existing rows have to
be removed. active_watchers is with temporary records, and I guess that
is the same with rls_watchers. No persistent data is to be lost, right?
Another one is extra_hdrs in silo table. I think it should be allowed to
be NULL or default '' (empty string), so stored messages will not be
lost - the check over the code showed inserting '' if no extra headers
are present at message storage time.
Cheers,
Daniel
</PRE>
</BLOCKQUOTE>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
</PRE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>