[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Fwd: LMDB and text encoding

To: openldap-devel@openldap.org
Subject: Re: Fwd: LMDB and text encoding
From: Timur Kristóf <timur.kristof@gmail.com>
Date: Wed, 7 Jun 2017 13:46:43 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=JTBJERf3KeIcprgHmF0NFUbAPjJXdIRXGVsBBPKfHUg=; b=o9HMCFjSRqo+Sep9IplGALcaGeQhGJqRWpaS6K1gOhiiCClKkP7mg3TKLXVSYV+zes JJG8MNuSPNqevfwOHvk2rGq4PPRLvXzY3wLq9/c+fQp8N4C8HupK00xB0hQi1vISZC/D gCxfLfQ+OvsoZiMK5msxYFnsis8/oPeRgYK+TASlwEByTliqlZcn4Mo+CWkmN4or16Lm HiXWKGnbbTOw+NegzejSJpTdUP0wRaKM6cNhf5atSQuV2X8fS83AEXqJXkaTEftFNyNi G5KT0iPWAvyjtfPEvSCBWUVVxU80j28g04kwPdGnWSaG+0j0WwDGmi3d6gtDucCDslP9 qd7A==
In-reply-to: <CAFF-SiVrxxSCNpJ+dMmBhx6X5UF7+hkOj5FuJ_3bzdu7NZQRJA@mail.gmail.com>
References: <CAFF-SiUrJKGvG_z5vKgn13KX6oSbWQmLDj0VqGXMsuzJT5JBEg@mail.gmail.com> <54CEE7F1.5020601@symas.com> <CAFF-SiW0VG6W0jMC=VrJgSTTL2S6bRAkKr25a3GFbF8JuCFS=w@mail.gmail.com> <CAFF-SiVN94zXibQ-sPHSX9z8qejPyCpMzBt-x1Zo8jW69+_QOA@mail.gmail.com> <54CF57CB.9000108@symas.com> <54CF6F74.3010009@usit.uio.no> <54CF7A88.7040801@symas.com> <54CF8E48.7040407@usit.uio.no> <CAFF-SiUtPwye6x0sCdJo=XgJqioyP3fpPw-XdnhqCbywQKpw2Q@mail.gmail.com> <87d25b18a3.fsf@mid.deneb.enyo.de> <CAFF-SiWbQgPoFE9SQSudXzuJPxg=+wM56DrraTX4QrvrBdKzxQ@mail.gmail.com> <87zj8fylgm.fsf@mid.deneb.enyo.de> <CAFF-SiVrxxSCNpJ+dMmBhx6X5UF7+hkOj5FuJ_3bzdu7NZQRJA@mail.gmail.com>

Hi Everyone,

I've just came accross this old thread and am wondering, is this still an issue?
Does LMDB have a way to use non-ASCII path names with mdb_env_open in a cross-platform way?

If not, would you guys accept patches to LMDB with this regard?

Thanks,

Timur

Prev by Date: Re: Status of ldap_init_fd and LDAP_PROTO_EXT?
Next by Date: Re: Fwd: LMDB and text encoding
Index(es):
- Chronological
- Thread