[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
valsort and telephone numbers
- To: openldap-technical@openldap.org
- Subject: valsort and telephone numbers
- From: Benin Technologies <benintechnologies@yahoo.fr>
- Date: Sun, 10 Feb 2013 20:08:34 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s1024; t=1360523320; bh=uIoiuhLil98lUs9njLkDt4p4EPDsJvSbCXna4323yH8=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=zioGiMT7BBrVxILMWtSggySLp7TmuFbpVTWKs/tjsTA9NBJKCZOxk0ZT7xnN1sXhJwytngRxpD1vVOys9s+YwqvX6GlyIBehhPkUvTbUajmColfPISyyPzPHZeWizykWatbftTNZK6CqlziQ6hvfqqPc98xg4CQ0jXLK/bc1h3k=
- User-agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
Hi,
Does anybody use the valsort overlay and its "weighted" method with
telephone numbers ?
Telephone numbers don't accept braces {} in their syntax, but the braces
are used by valsort to define the attribute's weight.
What's the best way around this ?
An easy way would be to create a custom myMobile attribute, with syntax
IA5 string (1.3.6.1.4.1.1466.115.121.1.26) instead of the telephone
number syntax (1.3.6.1.4.1.1466.115.121.1.50). IA5 strings accept braces
{}. But the tradeoff is that any string can be put in the myMobile
attribute.
The best way would be to enforce myMobile to accept only telephone
numbers (syntax 1.3.6.1.4.1.1466.115.121.1.50), PLUS braces {}
Can this be done ? any other idea ?