1. 21 May, 2012 2 commits
  2. 18 May, 2012 3 commits
  3. 17 May, 2012 2 commits
  4. 16 May, 2012 9 commits
  5. 15 May, 2012 1 commit
  6. 11 May, 2012 1 commit
  7. 08 May, 2012 4 commits
  8. 07 May, 2012 3 commits
    • Jelte Jansen's avatar
      [1208] use the container to set in-mem client · bf1717f3
      Jelte Jansen authored
      Instead of the direct shared_ptr.
      Changes needed:
      Moved loading of zones in config into the memory_datasrc implementation; at this moment the general API has no method for this (and it may not be necessary; datasources should handle their own config anyway).
      This does have one drawback; through the dynamic loading mechanism we currently lose exception type information. So for now specific exceptions such as MasterLoadError end up as 'general' DataSourceErrors. Tests have been updated to reflect this.
      Also, I made config handler slightly more lenient; it has hardcoded defaults and will now accept config parts without "class" or "zones"; using .spec -derived values is impractical here with the current config API, but in this case it shouldn't *really* matter; as IN is hardcoded in several places anyway atm.
    • Jelte Jansen's avatar
    • Jelte Jansen's avatar
      [1207] store and use raw inmem client pointer · 446e309a
      Jelte Jansen authored
      In order to add datasource factory, but keep current code working, store both the shared ptr (for reference counting) and the raw pointer it encapsulates. The latter is then used to call query::process().
  9. 19 Apr, 2012 5 commits
  10. 18 Apr, 2012 2 commits
  11. 17 Apr, 2012 4 commits
  12. 16 Apr, 2012 1 commit
    • Michal 'vorner' Vaner's avatar
      [1793] Tests for the loadzone command · 7f108b1a
      Michal 'vorner' Vaner authored
      It puts the configuration of the zone (which is loaded from SQLite3
      database) and the database at the disposition of the test. Then it asks
      it to load the zone and it expects it to load it.
  13. 09 Apr, 2012 2 commits
  14. 05 Apr, 2012 1 commit
    • JINMEI Tatuya's avatar
      [1788] removed the default for 'filetype' from the spec file. · efb79bb6
      JINMEI Tatuya authored
      for optional items setting the default doesn't make sense, but we also have
      test cases where syntax validation is skipped, so changing it to non-optional
      will break existing test cases.  at least for now, it seems to make most sense
      to keep it optional and define the default within the parser code.