Hello Greg,
Thanks, that sounds really reasonable. I'll have to get really
familiar with it, though.
First of all, I need Windows clients for offline use -- maybe cygwin will do.
Second, I don't exactly know what is the effect of disabling triggers
and rules: will it affect transactions running
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
First of all, I need Windows clients for offline use -- maybe cygwin will do.
Perhaps. Keep in mind the Bucardo daemon(s) can live
Dear Gurus,
I need some solution for a transaction-based system that may have
offline clients. Something like CVS in version management, but
SQL-based.
I need this because we have a team of 6 people, concurrently updating
shared XML files and such. When I leave the corporate network I can
keep
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
- Way of handling conflicting records
e.g. client A goes offline, client B modifies master, client A
modifies locally, and when goes online again cannot
