1. 02 Nov, 2006 1 commit
    • andrey@example.com's avatar
      Better fix for bug#22830 · c27a88ca
      andrey@example.com authored
      Events: crash with procedure which alters events with function
      
      Post-review CS
      
      This fix also changes the handling of KILL command combined with
      subquery. It changes the error message given back to "not supported",
      from parse error. The error for CREATE|ALTER EVENT has also been changed
      to generate "not supported yet" instead of parse error.
      In case of a SP call, the error is "not supported yet". This change
      cleans the parser from code which should not belong to there. Still
      LEX::expr_allows_subselect is existant because it simplifies the handling
       of SQLCOM_HA_READ which forbids subselects.
      c27a88ca
  2. 30 Oct, 2006 3 commits
  3. 27 Oct, 2006 2 commits
    • kroki/tomash@moonlight.intranet's avatar
      Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug22584 · db952c2f
      kroki/tomash@moonlight.intranet authored
      into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-bug22584
      db952c2f
    • kroki/tomash@moonlight.intranet's avatar
      BUG#22584: last_insert_id not updated after inserting a record through · 0e0f7a04
      kroki/tomash@moonlight.intranet authored
      a updatable view.
      
      When there's a VIEW on a base table that have AUTO_INCREMENT column, and
      this VIEW doesn't provide an access such column, after INSERT to such
      VIEW LAST_INSERT_ID() did not return the value just generated.
      
      This behaviour is intended and correct, because if the VIEW doesn't list
      some columns then these columns are effectively hidden from the user,
      and so any side effects of inserting default values to them.
      
      However, there was a bug that such statement inserting into a view would
      reset LAST_INSERT_ID() instead of leaving it unchanged.
      
      This patch restores the original value of LAST_INSERT_ID() instead of
      resetting it to zero.
      0e0f7a04
  4. 25 Oct, 2006 9 commits
  5. 24 Oct, 2006 5 commits
  6. 23 Oct, 2006 3 commits
  7. 20 Oct, 2006 10 commits
  8. 19 Oct, 2006 7 commits