diff options
| author | Matthias Dieter Wallnöfer <mwallnoefer@yahoo.de> | 2009-10-06 19:27:17 +0200 |
|---|---|---|
| committer | Matthias Dieter Wallnöfer <mwallnoefer@yahoo.de> | 2009-10-06 19:41:16 +0200 |
| commit | 8536e1b947ad8a2bc5596a9a1de9a58262153ebf (patch) | |
| tree | faac1f52c49a524211f8f80c56f525741c3b54e2 /source4/dsdb/samdb/ldb_modules/objectguid.c | |
| parent | 0d7c34a5b4362ae8b1083a8bcf3a4115c37cafde (diff) | |
| download | samba-8536e1b947ad8a2bc5596a9a1de9a58262153ebf.tar.gz samba-8536e1b947ad8a2bc5596a9a1de9a58262153ebf.tar.bz2 samba-8536e1b947ad8a2bc5596a9a1de9a58262153ebf.zip | |
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.
Diffstat (limited to 'source4/dsdb/samdb/ldb_modules/objectguid.c')
| -rw-r--r-- | source4/dsdb/samdb/ldb_modules/objectguid.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/source4/dsdb/samdb/ldb_modules/objectguid.c b/source4/dsdb/samdb/ldb_modules/objectguid.c index 3d218edc76..12dd402617 100644 --- a/source4/dsdb/samdb/ldb_modules/objectguid.c +++ b/source4/dsdb/samdb/ldb_modules/objectguid.c @@ -209,7 +209,7 @@ static int objectguid_add(struct ldb_module *module, struct ldb_request *req) ac, og_op_callback, req); if (ret != LDB_SUCCESS) { - return LDB_ERR_OPERATIONS_ERROR; + return ret; } /* go on with the call chain */ @@ -267,7 +267,7 @@ static int objectguid_modify(struct ldb_module *module, struct ldb_request *req) ac, og_op_callback, req); if (ret != LDB_SUCCESS) { - return LDB_ERR_OPERATIONS_ERROR; + return ret; } /* go on with the call chain */ |