1. 13 Mar, 2007 1 commit
  2. 10 Mar, 2007 1 commit
  3. 09 Mar, 2007 1 commit
  4. 08 Mar, 2007 5 commits
  5. 07 Mar, 2007 5 commits
  6. 05 Mar, 2007 4 commits
  7. 03 Mar, 2007 1 commit
    • evgen@sunlight.local's avatar
      Bug#25126: Wrongly resolved field leads to a crash. · 629c1231
      evgen@sunlight.local authored
      When the ORDER BY clause gets fixed it's allowed to search in the current
      item_list in order to find aliased fields and expressions. This is ok for a
      SELECT but wrong for an UPDATE statement. If the ORDER BY clause will
      contain a non-existing field which is mentioned in the UPDATE set list
      then the server will crash due to using of non-existing (0x0) field.
      
      When an Item_field is getting fixed it's allowed to search item list for
      aliased expressions and fields only for selects.
      629c1231
  8. 02 Mar, 2007 8 commits
  9. 01 Mar, 2007 8 commits
  10. 28 Feb, 2007 6 commits