1. 24 6月, 2020 3 次提交
  2. 23 6月, 2020 1 次提交
    • A
      fix of incorrect example · 72cddbe7
      Alexandr Kondratev 提交于
      was `curl -sS "<address>?param_id=2¶m_phrase=test" -d "SELECT * FROM table WHERE int_column = {id:UInt8} and string_column = {phrase:String}"`
      72cddbe7
  3. 19 6月, 2020 5 次提交
  4. 18 6月, 2020 4 次提交
  5. 16 6月, 2020 3 次提交
  6. 15 6月, 2020 1 次提交
    • L
      add mysql2ch in docs (#11680) · 6e18001b
      long2ice 提交于
      * add mysql2ch
      
      add mysql2ch
      
      * Update integrations.md
      
      * Update integrations.md
      
      * Update integrations.md
      
      * Update integrations.md
      
      * Update integrations.md
      
      * Update integrations.md
      
      * Update integrations.md
      6e18001b
  7. 12 6月, 2020 1 次提交
    • A
      Force table creation on SYSTEM FLUSH LOGS (v2) · 103eb171
      Azat Khuzhin 提交于
      After this patch SYSTEM FLUSH LOGS will force system.*_log table
      creatoins (only for enabled tables of course).
      
      This will avoid such hacks like:
      
         set log_queries=1;
         select 1;
         system flush logs;
      
      This is the second version of the patch, since first has a deadlock [1]
      (reported by @alesapin). This version does not use separate lock and do
      not issue CREATE TABLE from the query execution thread, instead it
      activate flushing thread to do so, hence this should be the same as if
      the table will be created during flush.
      
        [1]: https://gist.github.com/alesapin/d915d1deaa27d49aa31223daded02be2
      
      Fixes: #11563
      Cc: @alesapin
      Cc: @nikitamikhaylov
      103eb171
  8. 11 6月, 2020 3 次提交
  9. 08 6月, 2020 1 次提交
  10. 06 6月, 2020 1 次提交
  11. 05 6月, 2020 2 次提交
  12. 03 6月, 2020 1 次提交
  13. 02 6月, 2020 4 次提交
  14. 01 6月, 2020 2 次提交
  15. 29 5月, 2020 7 次提交
  16. 23 5月, 2020 1 次提交