Skip to content
  1. Apr 12, 2019
  2. Apr 10, 2019
  3. Apr 09, 2019
  4. Apr 08, 2019
  5. Apr 05, 2019
  6. Apr 04, 2019
  7. Apr 03, 2019
    • Richard Klees's avatar
      Setup: fixed odd missing database error (#25166) · 96bc811a
      Richard Klees authored
      The reason for this problem is some very chaotic handling of new instances of
      ilClient, caching in ilDbSetup and initialisation and distribution of database
      instances. ilClient::getDbSetup uses static methods from ilDbSetup that cache
      instances via client_id. The DBSetup instance is tied to the ilClient it was
      created. ilSetup produces two instances of ilClient, one for querying the status
      and one for actual actions on the client. The second instance is the one that is
      used to attempt login. Since ilDbSetup doesn't take into account that two
      instances for the same client might have been created, it returns a cached
      instance for the client id. This in fact is bound to the first ilClient instance
      and sets the db on that one (in provideGlobalDB) instead of setting the db on
      the second ilClient-instance which is the one that is in fact used afterwards.
      
      The problem at hand was solved by moving the caching of ilDbSetup instances to
      the ilClient. The root-cause was not solved here and the setup remains in its
      generally messy state for now.
      96bc811a
    • Alexander Killing's avatar
  8. Apr 02, 2019