git.samba.org / samba.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0d7c34a) | patch
s4:various LDB modules - "build_request" functions - propagate result codes back
authorMatthias Dieter Wallnöfer <mwallnoefer@yahoo.de>
Tue, 6 Oct 2009 17:27:17 +0000 (19:27 +0200)
committerMatthias Dieter Wallnöfer <mwallnoefer@yahoo.de>
Tue, 6 Oct 2009 17:41:16 +0000 (19:41 +0200)
commit8536e1b947ad8a2bc5596a9a1de9a58262153ebf
treefaac1f52c49a524211f8f80c56f525741c3b54e2tree
parent0d7c34a5b4362ae8b1083a8bcf3a4115c37cafdecommit | diff
s4:various LDB modules - "build_request" functions - propagate result codes back

It's very useful to know the exact result code when something fails and not
only a generic (by the module) created one.
Sure, there are some exception cases with specific results (special message
constellations, attributes, values...) which shouldn't be changed at all
(examples of them are in the "ldap.py" test). Therefore I looked very
carefully to not change them.
source4/dsdb/samdb/ldb_modules/kludge_acl.c diff | blob | history
source4/dsdb/samdb/ldb_modules/local_password.c diff | blob | history
source4/dsdb/samdb/ldb_modules/objectguid.c diff | blob | history
source4/dsdb/samdb/ldb_modules/partition.c diff | blob | history
source4/lib/ldb/modules/asq.c diff | blob | history
source4/lib/ldb/modules/paged_results.c diff | blob | history
source4/lib/ldb/modules/sort.c diff | blob | history
Samba Shared Repository