CVS log for servers/slapd/back-sql/rdbms_depend/pgsql/testdb_metadata.sql

Up to [OpenLDAP] / servers / slapd / back-sql / rdbms_depend / pgsql

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN
Current tag: MAIN

use RFC4523 objectClasses

fix ';binary' certificate transport (ITS#4868); add cert to sql-test000 (mysql; psql untested)

add delete stuff to all attributes (needed to deelete with "fail_if_no_mapping yes"); passes write test(s)

remove all referral specific code; now referrals can be used by defining appropriate data/metadata

map referrals in regular metadata structure (need to remove some of the specific code)

map referrals in regular metadata structure (need to remove some of the specific code)

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

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...

write test is almost working for ibmdb2 as well...

fix various issues; line up with new tests

further improve tests; line-up with code

now PostgreSQL seems to work...

update of RDBMS data for test031

fix duplicate key in metadata

should improve readability and (hopefully) decrease traffic on openldap-software; sorry I can't test it right now

table 'ldap_entries' must be aliased to allow filtering for DN-valued attrs

various fixes and improvements

CHANGES:
- 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

VERY PRELIMINARY support for PostgreSQL and IBM db2