[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Search Filter: Builtin Date/Time Functions?
- To: Brian Piesik <brian@vbguru.com>
- Subject: Re: Search Filter: Builtin Date/Time Functions?
- From: Michael Ströder <michael@stroeder.com>
- Date: Mon, 01 Dec 2003 08:18:33 +0100
- Cc: "'openldap-software'" <openldap-software@OpenLDAP.org>
- In-reply-to: <007801c3b75c$8950e440$9bfdc518@dev1>
- References: <007801c3b75c$8950e440$9bfdc518@dev1>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
Brian Piesik wrote:
ldapsearch "(&(radiusExpiration>=`date +%Y%m%d%H%M%S%z`))"
Here you are constructing a valid search filter with the help of shell
expanding/escaping etc.
Obviously modifying
OpenLDAP should prove the least amount of work since it's one application
used by many.
Not possible without violating the LDAP standard.
My plan is use a predefined string / parameter that would be parsed
internally by the server. An example would be something like:
(&(radiusExpiration>=getDate()))
1. You have to extend the LDAP standard for this to work. In particular this
affects the filter string representation. I'd suggest to read RFC 2254
before going any further.
2. This would be a server-side implementation of getDate() which is probably
not what you're after. Think of time sync problems...
Ciao, Michael.