On Sat, 2014-03-22 at 22:49 +, timur.kris...@gmail.com wrote:
When you operate on a dbi using a cursor and accidentally close the dbi before
committing the transaction of the cursor, mdb_txn_commit will return
MDB_BAD_VALSIZE. This is quite misleading because the problem doesn't actually
I wrote:
Let's see -- here are the options I can see (after an IRC chat):
(...)
2) Catch this case and instead return a generic something is
wrong - MDB_BAD_TXN or MDB_INCOMPATIBLE.
(...)
Duh, I forgot
(6) Like (2) but create a new error code after all. Then we can
document in its
Full_Name: Quanah Gibson-Mount
Version: openldap master
OS: Linux 2.6
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (75.111.58.125)
As reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741248, slapacl
when used with a base that is not contained in the OpenLDAP
qua...@openldap.org wrote:
Full_Name: Quanah Gibson-Mount
Version: openldap master
OS: Linux 2.6
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (75.111.58.125)
As reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741248,
slapacl
when used with a base that is