Can anyone spend a few words for me on the new "seq" column?
What's it's main purpose?
Is it functionally relevant or it something like a cache that can be
reset, modified or whatever with no big issues?
I'm used to move messages between mailboxes with queries like UPDATE
dbmail_messages SET mailbox_idnr = 89 WHERE mailbox_idnr = 47981; but
the seq column would be no more monotonically increasing in such case.
Is it a problem?
Futhermore in a dual master scenario the column doesn't seem really
replication-aware, so I was curious if having duplicates in it may be
problematic.
Thanks.
--
*Andrea Brancatelli
Schema31 S.p.a.
Responsabile IT*
ROMA - FIRENZE - PALERMO
ITALY
Tel: +39.06.98358472
Cell: +39.331.2488468
Fax: +39.055.71880466
Società del gruppo SC31 ITALIA
What's it's main purpose?
Is it functionally relevant or it something like a cache that can be
reset, modified or whatever with no big issues?
I'm used to move messages between mailboxes with queries like UPDATE
dbmail_messages SET mailbox_idnr = 89 WHERE mailbox_idnr = 47981; but
the seq column would be no more monotonically increasing in such case.
Is it a problem?
Futhermore in a dual master scenario the column doesn't seem really
replication-aware, so I was curious if having duplicates in it may be
problematic.
Thanks.
--
*Andrea Brancatelli
Schema31 S.p.a.
Responsabile IT*
ROMA - FIRENZE - PALERMO
ITALY
Tel: +39.06.98358472
Cell: +39.331.2488468
Fax: +39.055.71880466
Società del gruppo SC31 ITALIA