diff options
author | Kamen Mazdrashki <kamenim@samba.org> | 2010-12-10 02:55:30 +0200 |
---|---|---|
committer | Kamen Mazdrashki <kamenim@samba.org> | 2010-12-15 00:51:19 +0100 |
commit | c94e5d44385d23172a8776e4c12d71e30c9c6616 (patch) | |
tree | e1f390c5f3e67b240a15d67175f04296a04a31c8 /selftest/target/Samba4.pm | |
parent | afee8a28c408efd3323b9064929b00be6eb89815 (diff) | |
download | samba-c94e5d44385d23172a8776e4c12d71e30c9c6616.tar.gz samba-c94e5d44385d23172a8776e4c12d71e30c9c6616.tar.bz2 samba-c94e5d44385d23172a8776e4c12d71e30c9c6616.zip |
s4-repl: Allow dsdb_replicated_objects_commit() to use different schema while committing objects
working_schema is to be used while committing a Schema replica.
When we replicate Schema, then we most probably won't be
able to convert all replicated objects using the current
Schema cache (as we don't know anything about those new objects).
Thus, during Schema replication, we make a temporary
working_schema that contains both our current Schema +
all objects we get on the wire.
When we commit those new objects, we should use our working_schema
(by setting it to the ldb), and after all changes are commited,
we can refresh the schema cache so we have a brand new,
full-featured Schema cache
Diffstat (limited to 'selftest/target/Samba4.pm')
0 files changed, 0 insertions, 0 deletions