Skip to content
Snippets Groups Projects
  1. Dec 17, 2021
  2. Dec 16, 2021
    • Igor Kuznetsov's avatar
      feat: migrate to lua table for executing query result · df21abe1
      Igor Kuznetsov authored
      Was fixed interaction format between lua and sbroad rust lib. In current implementation sbroad encodes query result to yaml and send it to lua app. Lua app gives yaml and decodes it to lua table. After apply this changes lua app will receive lua table and yaml transformations will not be needed.
      df21abe1
  3. Dec 14, 2021
  4. Dec 10, 2021
  5. Dec 09, 2021
  6. Dec 08, 2021
  7. Dec 07, 2021
  8. Dec 06, 2021
  9. Dec 03, 2021
  10. Dec 02, 2021
  11. Dec 01, 2021
  12. Nov 30, 2021
  13. Nov 29, 2021
    • Denis Smirnov's avatar
      feat: implement IR · dc83f9e7
      Denis Smirnov authored
      At the moment IR (logical plan) is far from final release. Current
      commit fixes some point on a way to the final API and full test
      coverage.
      dc83f9e7
    • Igor Kuznetsov's avatar
      refactoring: extact working with lua to struct · e10c70ce
      Igor Kuznetsov authored
      It was done that decrease coupling working with lua in code and make
      migration to rust module master branch more simple. Besides was fixed bug for working with query string variable in execute_sql function in unsafe block, because in this place was buffer overflow.
      e10c70ce
  14. Nov 25, 2021
  15. Nov 23, 2021
  16. Nov 22, 2021
    • Denis Smirnov's avatar
      feat: implement relation ir · ee45da42
      Denis Smirnov authored
      1. Implement columns (with types) and tables as a part of IR.
      2. Use serde deserialization trait to build tables from YAML files.
         It would be also helpful when writing tests for arbitrary plan
         transformations.
      ee45da42
  17. Nov 19, 2021
    • Denis Smirnov's avatar
      fix: please cargo pedantic for the schema · a817ec34
      Denis Smirnov authored
      a817ec34
    • Denis Smirnov's avatar
      feat: implement values for ir · c71b5c38
      Denis Smirnov authored
      To work with Calcite and Tarantool the planner needs to store values
      in the plan leaf nodes. These values should be defined with exact types.
      At the moment we need only several primitive types:
      - boolean
      - null
      - number (decimal from decnumber library)
      - string
      
      As the planner analyzes SQL, it has to work with tree-valued logic
      (3VL). At the moment we'll need only equivalence operation, so it
      was implemented for the values in a 3VL manner.
      c71b5c38
  18. Nov 16, 2021
  19. Nov 12, 2021
Loading