Hi Cedric,
This will result into inconsistencies. I'll explain by example.
Server 1 is the read-only server, server 2 is the write-only server.
The imap server will do a select on a folder through server 1. The user
deletes a few messagess from this folder (which will be sent as an
update to s
Hi,
I must say that Klas's approach seems to be the best to me. MySQL
already has
very acceptable support for replication and it would be foolish to rely on a
script based solution that will never work half as well. PostgreSQL also has
one or two replication implementations/projects if
On Fri, 2002-12-06 at 03:31, Roel Rozendaal - IC&S wrote:
> Hi Klas,
>
> Our plan for the moment is to have two databases: one used in
> production and the other as hot spare. When the live machine is used,
> the succesfull update/insert/delete queries are performed at the hot
> spare as well
Hi Klas,
we are currently looking out for some kind of replication - your way of
doing it is interesting. However I would prefer a system where the
replication is completely transparent for dbmail mainly because of
postgresql/other database support: one of the main objectives of dbmail
is com
