Thanks p.. I did some more testing and you are right. It is a RDBMS problem. This is what I found (tested with iSQL and directly on the RDBMS).
In chronological order:
- SET autocommit=0
- SELECT @@autocommit -> result: 0, it is turned off
This is standard slapd/back-sql config.
- SELECT * FROM ldap_entries -> 10 results
- Now I change the data directly using a different connection and other
GUI. I add a record (and commit it). 5. SELECT * FROM ldap_entries -> 10 results
The latter result surprised me. So if data is changed by another connection, it will not be refresh data on other connections.
- COMMIT
- SELECT * FROM ldap_entries -> 11 results
So, in order to refresh data, slapd has to prepend every read operation with a COMMIT. This is not logical, is it?
So, I believe adding a configuration option, for people who want to use back-sql with MySQL/InnoDB, could be a handy solution. Where can I add this feature request?
You may reference this thread (point to the relevant message from the official archives).
p.