1. 29 Nov, 2006 1 commit
    • evgen@moonbone.local's avatar
      Bug#20327: Marking of a wrong field leads to a wrong result on select with view, · e851a9ea
      evgen@moonbone.local authored
      prepared statement and subquery.
      
      When a field of a view from an outer select is resolved the find_field_in_view
      function creates an Item_direct_view_ref object that references the 
      corresponding view underlying field. After that the view_ref is marked
      as a dependent one. While resolving view underlying field it also get
      marked as a dependent one due to current_select still points to the subselect.
      Marking the view underlying field is wrong and lead to attaching conditions
      to a wrong table and thus to the wrong result of the whole statement.
      
      Now mark_select_range_as_dependent() function isn't called for fields from a 
      view underlying table.
      e851a9ea
  2. 09 Nov, 2006 3 commits
  3. 08 Nov, 2006 3 commits
  4. 07 Nov, 2006 9 commits
  5. 06 Nov, 2006 6 commits
  6. 03 Nov, 2006 1 commit
    • gkodinov/kgeorge@macbook.gmz's avatar
      Bug #22457: Column alias in ORDER BY works, but not if in an expression · 77acba32
      gkodinov/kgeorge@macbook.gmz authored
       The parser is allocating Item_field for references by name in ORDER BY
       expressions. Such expressions however may point not only to Item_field 
       in the select list (or to a table column) but also to an arbitrary Item. 
       This causes Item_field::fix_fields to throw an error about missing 
       column.
       The fix substitutes Item_field for the reference with an Item_ref when 
       not pointing to Item_field.
      77acba32
  7. 01 Nov, 2006 4 commits
  8. 31 Oct, 2006 8 commits
  9. 30 Oct, 2006 1 commit
  10. 25 Oct, 2006 1 commit
  11. 24 Oct, 2006 3 commits