summaryrefslogtreecommitdiff
path: root/source4/dsdb/samdb/ldb_modules/repl_meta_data.c
AgeCommit message (Collapse)AuthorFilesLines
2007-10-10r21842: fix typo in commentStefan Metzmacher1-12/+12
metze (This used to be commit 8fcd5209ae46823f7d99bddff6e61873e75dd24c)
2007-10-10r21839: add my email addressStefan Metzmacher1-1/+1
metze (This used to be commit e3be33c1d9f9e44ef37e6ef72a23576474f6e725)
2007-10-10r21838: generate no metadata for constructed attributesStefan Metzmacher1-2/+4
metze (This used to be commit 7e0620e524886a66dbdb16f35fee4f51f2867a2a)
2007-10-10r21773: fix typo orginating -> originatingStefan Metzmacher1-7/+7
and use the struct member names in all cases metze (This used to be commit c543ee57454d006c545e3e9e20c9ac0114081d3d)
2007-10-10r21496: A number of ldb control and LDAP changes, surrounding theAndrew Bartlett1-1/+1
'phantom_root' flag in the search_options control - Add in support for LDB controls to the js layer - Test the behaviour - Implement support for the 'phantom_root' flag in the partitions module - Make the LDAP server set the 'phantom_root' flag in the search_options control - This replaces the global_catalog flag passed down as an opaque pointer - Rework the string-format control parsing function into ldb_parse_control_strings(), returning errors by ldb_errorstring() method, rather than with printf to stderr - Rework some of the ldb_control handling logic Andrew Bartlett (This used to be commit 2b3df7f38d7790358dbb4de1b8609bf794a351fb)
2007-10-10r21465: the LDAP-UPTODATEVECTOR test shows that the replUpToDateVectorStefan Metzmacher1-37/+11
doesn't contain an entry for the local invocation_id metze (This used to be commit 4bd0ddeb80b0a6695a457434594c0240c8880d9f)
2007-10-10r20975: - implement handling of meta data an on originating addStefan Metzmacher1-37/+240
there're a few things TODO, but it's a good start we need to research if an originating change causes the replUpToDateVector attribute to change...(I assume it, but needs testing) metze (This used to be commit fde0aabd9ae79fcefbcba34e6f9143f93ffcf96c)
2007-10-10r20971: we don't need this check twice:-)Stefan Metzmacher1-7/+0
metze (This used to be commit b7d48274a7341c5e4a3f103387f87fcc94853271)
2007-10-10r20968: - add functions to sort the meta data and attribute arraysStefan Metzmacher1-25/+90
- we should use them before we store records to disk metze (This used to be commit a5200ef0cae5e8b0cedf196c9d76afc46e08c316)
2007-10-10r20864: move common stuff into an extra functionStefan Metzmacher1-85/+62
metze (This used to be commit 3f441741a6ff00ba88d3134c97e597285afbfed7)
2007-10-10r20863: check that there's a current partition control attached to the requestStefan Metzmacher1-6/+65
metze (This used to be commit b1377a2e240dbe36277816452d33d6abaa486b9e)
2007-10-10r20776: require a loaded dsdb_schema for originating add and modify operationsStefan Metzmacher1-6/+26
(later we'll require it for all originating changes...) metze (This used to be commit fc1a836eccc0913fdab644341fa3e37a2f086de8)
2007-10-10r20729: add a version number to struct dsdb_extended_replicated_objectsStefan Metzmacher1-0/+7
metze (This used to be commit 2e79863d54030526841e5858e7be6a815c25593b)
2007-10-10r20728: the DSDB_CONTROL_REPLICATED_OBJECT_OID control isn't used anymoreStefan Metzmacher1-50/+0
because we now use DSDB_EXTENDED_REPLICATED_OBJECTS_OID extended operation metze (This used to be commit 4380cc9ed6ac2e6c133b5a36f922b341474a8e7e)
2007-10-10r20727: implement basic merging of replicated objects when it already existStefan Metzmacher1-4/+246
in the ldb metze (This used to be commit 262e42123d0bca77560fbb5a33c13a9c275ba3ec)
2007-10-10r20726: - only add the rdn attribute and it's meta_data when the 'name' ↵Stefan Metzmacher1-0/+19
attribute is there - add the values for objectGUID and whenChanged inside the ldb module, so that the ldb module has only replicated attributes as input metze (This used to be commit 0ecb07e0526462529fb21cec30e789a9002b30a1)
2007-10-10r20713: sort the cursors in replUpToDateVector by source_dsa_invocation_id,Stefan Metzmacher1-0/+13
w2k3 seems to do the same. It's later useful, when we would have a large array be could use a binary search metze (This used to be commit cd654f20e16c32f82ceb2b66453ce8d1be7020dd)
2007-10-10r20710: update or create the "repsFrom" values after applying replicated objectsStefan Metzmacher1-1/+93
metze (This used to be commit 665d8f9626f8ef1c64f6fac79bdc40d14330f126)
2007-10-10r20709: pass a repsFromTo1 struct down as it contains all needed info for ↵Stefan Metzmacher1-4/+7
the source dsa and the highwater mark vector metze (This used to be commit a31e017e5388e5abd6ed9d09adcf26d2527954a6)
2007-10-10r20705: store the "replUpToDateVector" attribute in ↵Stefan Metzmacher1-2/+335
DSDB_EXTENDED_REPLICATED_OBJECTS metze (This used to be commit c9e7a58f6a16dfa28323fd0fd01ad6ee516c51b0)
2007-10-10r20681: implement the DSDB_EXTENDED_REPLICATED_OBJECTS operation.Stefan Metzmacher1-2/+373
the merging of existing objects is not implemented yet... there are a few ifdef REPLMD_FULL_ASYNC because we need to workarouns ldb's async infrastructure (which don't handle full async sub requests nicely) metze (This used to be commit da4ff0e7ccde47b3e092313ba22422350cf50f78)
2007-10-10r20587: prepare the DSDB_EXTENDED_REPLICATED_OBJECTS_OID handlingStefan Metzmacher1-0/+16
metze (This used to be commit ef3b325db060d43a7c2e058f6b8914b5867cd321)
2007-10-10r20580: pass the DSDB_CONTROL_REPLICATED_OBJECT_OID with the ldb_add requestStefan Metzmacher1-17/+78
when applying replicated objects. the samldb module ignores such requests now... and the repl_meta_data module has different functions for the replicated and originating cases... metze (This used to be commit a4d5e0126cfd6135ab829f4984269e265a868a28)
2007-10-10r20522: make a copy of the objectguid ldb module because:Stefan Metzmacher1-0/+262
- I'll add handling of replication meta data to it for orginating changes - I'll pass replication meta data via a ldb control for applying replicated changes - It will also update the replUpToDateVector attribute in in root object of the partition - It will handle deleted records by adding the isDeleted=TRUE attribute and move them to the CN=Deleted Objects container of the partition - I make a copy to play with the code without breaking the LDAP backend setup metze (This used to be commit 045ddfe1ec626fab5e8fd75c5b47f0525b7ebb01)