- Jan 18, 2005
-
-
Pierangelo Masarati authored
-
Pierangelo Masarati authored
fix different issues with referrals in searches; remove unused tests; cleanup referrals in tests so that they don't get chased; improve schema checking in modrdn and updates in general; minor cleanup
-
- Aug 25, 2004
-
-
Pierangelo Masarati authored
more definitive improvements; now write operations are consistent; plugged some more leaks/invalid frees; tests are more complete. IBM db2 doesn't pass write test because the entries are written in a different order; need to write a script that sorts the results...
-
- Aug 24, 2004
-
-
Pierangelo Masarati authored
-
Pierangelo Masarati authored
-
- Aug 21, 2004
-
-
Pierangelo Masarati authored
-
- Aug 20, 2004
-
-
Pierangelo Masarati authored
-
Pierangelo Masarati authored
-
- Jan 31, 2004
-
-
Pierangelo Masarati authored
-
- Jan 16, 2004
-
-
Pierangelo Masarati authored
should improve readability and (hopefully) decrease traffic on openldap-software; sorry I can't test it right now
-
- Jan 09, 2004
-
-
Pierangelo Masarati authored
-
- Sep 02, 2002
-
-
Pierangelo Masarati authored
-
- Aug 16, 2002
-
-
Pierangelo Masarati authored
- now all write operations appear to work correctly with PostgeSQL 7.0 - all write operations have been made transactional (atomic writes to entries are committed separately only in case of complete^1 success while all other operations are rolled-back by default) - more cleanup and handling of exceptional conditions TODO: - deen to check with different databases and more up to date versions of both unixODBC and PostgreSQL. ^1: attribute add/modify/delete operations silently succeed if the appropriate add/delete proc does not exist for each attribute; this may be correct to hide undesired/unimplemented correspondence between LDAP and SQL databases; however, a more appropriate LDAP behavior would be a failure with LDAP_UNAVAILABLE if a single write operation cannot be executed for such reason
-
- Aug 13, 2002
-
-
Pierangelo Masarati authored
-