1. 15 Dec, 2016 1 commit
  2. 27 Jun, 2016 1 commit
  3. 02 May, 2016 1 commit
  4. 11 Apr, 2016 1 commit
  5. 20 Jan, 2016 1 commit
  6. 17 Dec, 2015 1 commit
  7. 04 Dec, 2015 1 commit
  8. 30 Oct, 2015 1 commit
  9. 01 Oct, 2015 1 commit
  10. 29 Sep, 2015 1 commit
  11. 03 Sep, 2015 1 commit
  12. 06 Aug, 2015 2 commits
  13. 11 Jun, 2015 1 commit
  14. 10 Jun, 2015 1 commit
  15. 08 Jun, 2015 1 commit
  16. 20 May, 2015 1 commit
  17. 12 May, 2015 1 commit
  18. 09 Apr, 2015 1 commit
  19. 22 Oct, 2014 1 commit
  20. 24 Sep, 2014 1 commit
  21. 12 Sep, 2014 1 commit
  22. 13 Aug, 2014 1 commit
  23. 04 Aug, 2014 1 commit
  24. 01 Aug, 2014 1 commit
  25. 31 Jul, 2014 1 commit
  26. 27 May, 2014 2 commits
  27. 10 Apr, 2014 1 commit
  28. 09 Apr, 2014 2 commits
  29. 07 Apr, 2014 1 commit
  30. 03 Apr, 2014 1 commit
  31. 27 Mar, 2014 1 commit
  32. 19 Mar, 2014 1 commit
  33. 18 Mar, 2014 2 commits
  34. 14 Mar, 2014 1 commit
    • Marek Vavruša's avatar
      query_module: configurable query processing modules · 3c745f0b
      Marek Vavruša authored
      Current API provides a "query plan" for each zone, which is
      basically a set of steps it needs to takes a query to be resolved.
      The plan is divided into several stages that reflect answer section
      processing. Now this query plan can be altered via configurable modules,
      first module is a 'synth_record' that makes synthetic forward/reverse
      records if the query isn't satisfied from the zone contents.
      3c745f0b