You can also have a trigger that records into a log table the id & table of
each record inserted/updated/deleted, and then it's a simple matter of
merging changes from a certain point forward by searching that table and
using the values of the current records.
--
Scott Ribe
[EMAIL PROTECTED]
http
On 8/7/07, Owen Hartnett <[EMAIL PROTECTED]> wrote:
> At 2:15 PM -0700 8/7/07, Ben wrote:
> >How many users do you have? Have you considered giving each user a
> >schema in which to make their changes? It sounds like you don't
> >really have a multi-master replication issue, which makes things
> >e
You can group schemas with views, and it guarentees nobody will accidently
overwrite somebody else's stuff. Merging a two schemas with identical
table structure should also be quite trivial. Of course, if you have a lot
of users, this might not work so well
On Tue, 7 Aug 2007, Owen Hartnet
At 5:13 PM -0500 8/7/07, Scott Marlowe wrote:
On 8/7/07, Owen Hartnett <[EMAIL PROTECTED]> wrote:
Here's what I want to do:
Checkpoint the database in whatever way is appropriate.
Make copies of the database on several laptops for use in the field
(in automobiles) to do database changes.
At 2:15 PM -0700 8/7/07, Ben wrote:
How many users do you have? Have you considered giving each user a
schema in which to make their changes? It sounds like you don't
really have a multi-master replication issue, which makes things
easier.
Maybe I'm not understanding the strategy, but I don't
On 8/7/07, Owen Hartnett <[EMAIL PROTECTED]> wrote:
>
> Here's what I want to do:
>
> Checkpoint the database in whatever way is appropriate.
>
> Make copies of the database on several laptops for use in the field
> (in automobiles) to do database changes. Record all the changes made
> since the c
How many users do you have? Have you considered giving each user a schema
in which to make their changes? It sounds like you don't really have a
multi-master replication issue, which makes things easier.
On Tue, 7 Aug 2007, Owen Hartnett wrote:
Here's what I want to do:
Checkpoint the datab
Here's what I want to do:
Checkpoint the database in whatever way is appropriate.
Make copies of the database on several laptops for use in the field
(in automobiles) to do database changes. Record all the changes made
since the checkpoint as the user makes them.
Periodically take all the
