# HG changeset patch
# User Pierre-Yves David <pierre-yves.david@logilab.fr>
# Date 1366732700 -7200
# Node ID 192a748550c7311bcf39755a4e5e91e78c0131cc
# Parent  9edfa3660bf4e6d93e2fcdce00cedc861d44a962
[test/ldap] have RQL2LDAPFilterTC use its own database

I do not know what RQL2LDAPFilterTC is about and why it does this strange reuse
of LDAPUserSourceTC pre_setup_database but it is certainly a good idea to have it
use a dedicated database-cache.

diff -r 9edfa3660bf4 -r 192a748550c7 server/test/unittest_ldapsource.py
--- a/server/test/unittest_ldapsource.py	Tue Apr 23 16:25:56 2013 +0200
+++ b/server/test/unittest_ldapsource.py	Tue Apr 23 17:58:20 2013 +0200
@@ -614,8 +614,8 @@
 
     def setUp(self):
         self.handler = get_test_db_handler(LDAPUserSourceTC.config)
-        self.handler.build_db_cache('ldap-user', LDAPUserSourceTC.pre_setup_database)
-        self.handler.restore_database('ldap-user')
+        self.handler.build_db_cache('ldap-rqlgenerator', LDAPUserSourceTC.pre_setup_database)
+        self.handler.restore_database('ldap-rqlgenerator')
         self._repo = repo = self.handler.get_repo()
         self._schema = repo.schema
         super(RQL2LDAPFilterTC, self).setUp()