Skip to content
Snippets Groups Projects
  1. Nov 03, 2013
  2. Nov 02, 2013
  3. Nov 01, 2013
  4. Oct 30, 2013
  5. Oct 17, 2013
  6. Oct 16, 2013
  7. Oct 10, 2013
  8. Oct 06, 2013
  9. Aug 19, 2013
  10. Jul 11, 2013
  11. Jul 10, 2013
  12. Jun 28, 2013
  13. Jun 24, 2013
  14. Jun 20, 2013
  15. Jun 18, 2013
    • Konstantin Osipov's avatar
      tuple-access: code review fixes · af4164fb
      Konstantin Osipov authored
      Two significant changes (both arguable, since this patch is about
      taste by a large measure):
      
      1) Split tuple_seek() into two: tuple_rewind()
      and tuple_seek().
      
      tuple_rewind() simply initializes the iterator and
      sets it to 'before-first' position.
      tuple_seek() returns a field, and sets the iterator
      to the position after the returned field.
      
      Previosly there was only tuple_seek(), which required
      tuple_next() to get the field, and it was confusing whether
      or not tuple_next() after tuple_seek() is required.
      Indeed, the very code I chagned sometimes would
      call tuple_next() after tuple_seek() and sometimes would not.
      
      2) Move the return value of the iterator outside
      of iteration state.
      
      The advantage of "binding" the out parameters of the iterator to
      iterator state is that you bind once, and don't need to supply out
      parameters into every call to tuple_next() function. It also makes
      it easy to add extra out parameters for bind in the future (field
      data type, flags, etc).
      
      This makes "binding" technique popular in database driver
      APIs. Binding makes API more stable, which is also
      important in drivers.
      
      In this case, however, binding adds for extra lines of code
      and (possibly) few extra instructions. Plus, since
      this is an internal API which we can change any day,
      its stability is not as important. So it seems that for
      now we're better of with an API which is a bit
      more concise/efficient, and can switch to using binding later,
      if needed.
      af4164fb
    • Dmitry E. Oboukhov's avatar
      a3767dcc
  16. Jun 14, 2013
  17. Jun 08, 2013
  18. Jun 07, 2013
  19. Jun 06, 2013
  20. Jun 05, 2013
  21. Jun 04, 2013
  22. Jun 02, 2013
  23. May 16, 2013
  24. May 04, 2013
    • Konstantin Osipov's avatar
      Tarantool/Box -> Tarantool. · 6af037d1
      Konstantin Osipov authored
      This messes the old "core/module" paradigm quite a bit, but Box,
      while a neat name, was confusing people.
      
      tarantool_box is preserved as the daemon name.
      6af037d1
  25. Apr 25, 2013
  26. Apr 10, 2013
  27. Mar 26, 2013
    • Konstantin Osipov's avatar
      Fix broken (crashing) command line client on Ubuntu Precise · 3219428f
      Konstantin Osipov authored
      libreadline already goes with libhistory compiled in,
      no reason to add it to the dynamically linked library
      list.
      Apparently, explicitly listing libhistory leads to
      the dl loader pre-loading it instead of the compiled-in
      version, which, in turn, leads to a crash on the first
      history search in the command line client.
      
      The fix is to remove cmake dependency on libhistory
      as well as on libncurses, which we don't need either
      (always require libtermcap).
      3219428f
Loading