
CVS log for servers/slapd/back-sql/rdbms_depend/pgsql/testdb_create.sql
Up to [OpenLDAP] / servers / slapd / back-sql / rdbms_depend / pgsql
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Current tag: OPENLDAP_REL_ENG_2_2_19
Revision 1.2: download - view: text, markup - select for diffs
Fri Aug 16 14:45:24 2002 UTC (20 years, 5 months ago) by ando
Branches: MAIN
CVS tags: OPENLDAP_REL_ENG_2_2_BP,
OPENLDAP_REL_ENG_2_2_9,
OPENLDAP_REL_ENG_2_2_8,
OPENLDAP_REL_ENG_2_2_7,
OPENLDAP_REL_ENG_2_2_6,
OPENLDAP_REL_ENG_2_2_5,
OPENLDAP_REL_ENG_2_2_4,
OPENLDAP_REL_ENG_2_2_3BETA,
OPENLDAP_REL_ENG_2_2_30,
OPENLDAP_REL_ENG_2_2_2BETA,
OPENLDAP_REL_ENG_2_2_29,
OPENLDAP_REL_ENG_2_2_28,
OPENLDAP_REL_ENG_2_2_27,
OPENLDAP_REL_ENG_2_2_26,
OPENLDAP_REL_ENG_2_2_25,
OPENLDAP_REL_ENG_2_2_24,
OPENLDAP_REL_ENG_2_2_23,
OPENLDAP_REL_ENG_2_2_22,
OPENLDAP_REL_ENG_2_2_21,
OPENLDAP_REL_ENG_2_2_20,
OPENLDAP_REL_ENG_2_2_1BETA,
OPENLDAP_REL_ENG_2_2_19,
OPENLDAP_REL_ENG_2_2_18,
OPENLDAP_REL_ENG_2_2_17,
OPENLDAP_REL_ENG_2_2_16,
OPENLDAP_REL_ENG_2_2_15,
OPENLDAP_REL_ENG_2_2_14,
OPENLDAP_REL_ENG_2_2_13,
OPENLDAP_REL_ENG_2_2_12,
OPENLDAP_REL_ENG_2_2_11,
OPENLDAP_REL_ENG_2_2_10,
OPENLDAP_REL_ENG_2_2_0ALPHA,
OPENLDAP_REL_ENG_2_2,
OPENLDAP_REL_ENG_2_1_MP,
NO_SLAP_OP_BLOCKS
Branch point for: OPENLDAP_REL_ENG_2_1
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +23 -22
lines
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
______________
© Copyright 1998-2020,
OpenLDAP Foundation, info@OpenLDAP.org