1. 24 5月, 2018 2 次提交
  2. 23 5月, 2018 1 次提交
  3. 17 5月, 2018 1 次提交
  4. 16 5月, 2018 1 次提交
  5. 01 5月, 2018 1 次提交
  6. 19 4月, 2018 4 次提交
  7. 18 4月, 2018 1 次提交
  8. 17 4月, 2018 2 次提交
  9. 16 4月, 2018 1 次提交
  10. 04 4月, 2018 2 次提交
  11. 30 3月, 2018 1 次提交
  12. 07 3月, 2018 2 次提交
  13. 28 2月, 2018 1 次提交
  14. 16 2月, 2018 2 次提交
  15. 14 2月, 2018 2 次提交
  16. 13 2月, 2018 1 次提交
  17. 10 2月, 2018 1 次提交
  18. 09 2月, 2018 1 次提交
  19. 30 1月, 2018 2 次提交
  20. 23 1月, 2018 1 次提交
  21. 20 1月, 2018 1 次提交
  22. 17 1月, 2018 1 次提交
  23. 14 12月, 2017 1 次提交
  24. 15 11月, 2017 2 次提交
  25. 08 11月, 2017 1 次提交
  26. 30 10月, 2017 2 次提交
    • M
      * Modify pack/unpack functions for new eos::string type · 379686a1
      Matias Romeo 提交于
      * Fix simpledb contract
      379686a1
    • M
      First approach to support reading of variable length messages. · 37ba0cd9
      Matias Romeo 提交于
      Under this approach the functions in simpledb.gen.hpp can be auto-generated using the ABI definition.
      
      In particular the specialization for currentMessage must only be defined if the
      struct has at least one variable length type (String, Bytes, etc), otherwise the default function will do ok.
      
      The functions valueToBytes/bytesToValue must only be defined when the table is a KeyValue table.
      These are required because the underlying db functions receives and
      returns the serialized version of the value.
      
      Then we can simplify the interface for the C++ helper VarTable (maybe reanaming to KeyValueTable?)
      specifying the KeyType and the ValueType.
      
      template<AccountName scope, AccountName code, TableName table,
      typename KeyType, typename ValueType>
      struct KeyValueTable
      
      and inside the store/load functions (table_impl_obj) we need to call valueToBytes/bytesToValue accordingly.
      
      Ref #492
      37ba0cd9
  27. 12 10月, 2017 1 次提交
  28. 14 9月, 2017 1 次提交