1. 11 8月, 2021 2 次提交
  2. 10 8月, 2021 1 次提交
  3. 09 8月, 2021 1 次提交
  4. 06 8月, 2021 2 次提交
  5. 28 7月, 2021 2 次提交
  6. 27 7月, 2021 1 次提交
  7. 26 7月, 2021 2 次提交
  8. 23 7月, 2021 1 次提交
  9. 22 7月, 2021 2 次提交
  10. 21 7月, 2021 1 次提交
  11. 19 7月, 2021 2 次提交
  12. 17 7月, 2021 3 次提交
  13. 16 7月, 2021 1 次提交
  14. 15 7月, 2021 2 次提交
  15. 14 7月, 2021 3 次提交
  16. 13 7月, 2021 1 次提交
  17. 10 7月, 2021 2 次提交
  18. 09 7月, 2021 2 次提交
  19. 02 7月, 2021 1 次提交
  20. 01 7月, 2021 2 次提交
  21. 30 6月, 2021 1 次提交
    • J
      fix: initialize ServiceLoaders from the FunctionFactory class loader (#1172) · d91b6258
      Jon Bratseth 提交于
      In environments where the QuestDb classes are not loaded by the system
      class loader and no context class loader is explicitly set, functions
      will not be found when initializing a ServiceLoader without passing
      a class loader explicitly.
      
      This change will always work assuming that SQL functions are loadable
      from the same class loader as FunctionFactory, that is, there is no support
      for plugging in external functions by passing a class loader capable of loading
      those classes. I think that assumption is true for QuestDb as I can't find
      any mention of class loaders in the QuestDb doc, and it would be challenging to
      make this work because the external class loader would also need to correctly
      load the functions bundled with QuestDb.
      d91b6258
  22. 29 6月, 2021 2 次提交
  23. 26 6月, 2021 1 次提交
  24. 25 6月, 2021 1 次提交
  25. 24 6月, 2021 1 次提交