An error occurred fetching the project authors.
  1. 20 Sep, 2007 1 commit
  2. 05 Jul, 2007 1 commit
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #29166: · 1532452a
      gkodinov/kgeorge@magare.gmz authored
      AsText() needs to know the maximum number of
      characters a IEEE double precision value can
      occupy to make sure there's enough buffer space.
      The number was too small to hold all possible
      values and this caused buffer overruns.
      Fixed by correcting the calculation of the 
      maximum digits in a string representation of an
      IEEE double precision value as printed by 
      String::qs_append(double).
      1532452a
  3. 07 Jun, 2007 1 commit
    • evgen@moonbone.local's avatar
      Bug#28763: Selecting geometry fields in UNION caused server crash. · eb9e174b
      evgen@moonbone.local authored
      This bug was introduced by the fix for the bug#27300. In this fix a section
      of code was added to the Item::tmp_table_field_from_field_type method.
      This section intended to create Field_geom fields for the Item_geometry_func
      class and its descendants. In order to get the geometry type of the current
      item it casted "this" to the Item_geometry_func* type. But the
      Item::tmp_table_field_from_field_type method is also used for creation of
      fields for UNION and in this case this method is called for an object of the
      Item_type_holder class and the cast to the Item_geometry_func* type causes 
      a server crash.
      
      Now the Item::tmp_table_field_from_field_type method correctly works when it's
      called for both the Item_type_holder and the Item_geometry_func classes.
      The new geometry_type variable is added to the Item_type_holder class.
      The new method called get_geometry_type is added to the Item_field
      and the Field classes. It returns geometry type from the field for the
      Item_field and the Field_geom classes and fails an assert for other Field
      descendants.
      eb9e174b
  4. 28 Mar, 2007 1 commit
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #27300: · c3eb3f70
      gkodinov/kgeorge@magare.gmz authored
        Geometry fields have a result type string and a 
        special subclass to cater for the differences
        between them and the base class (just like 
        DATE/TIME).
        When creating temporary tables for results of 
        functions that return results of type GEOMETRY
        we must construct fields of the derived class 
        instead of the base class.
        Fixed by creating a GEOMETRY field (Field_geom) 
        instead of a generic BLOB (Field_blob) in temp 
        tables for the results of GIS functions that 
        have GEOMETRY return type (Item_geometry_func).
      c3eb3f70
  5. 26 Mar, 2007 1 commit
    • gkodinov/kgeorge@magare.gmz[kgeorge]'s avatar
      Bug #27164: not reseting the data pointer · e6d81ad3
      gkodinov/kgeorge@magare.gmz[kgeorge] authored
       to 0 causes wrong (large) length to be read
       from the row in _mi_calc_blob_length() when 
       storing NULL values in (e.g) POINT columns.
       This large length is then used to allocate
       a block of memory that (on some OSes) causes
       trouble.
       Fixed by calling the base class's 
       Field_blob::reset() from Field_geom::reset()
       that is called when storing a NULL value into
       the column.
      e6d81ad3
  6. 23 Mar, 2007 1 commit
    • tsmith@siva.hindu.god's avatar
      Bug #24563: MBROverlaps does not seem to function propertly. · 47cce188
      tsmith@siva.hindu.god authored
      Fix is to rewrite the MBR::overlaps() function, to compute the dimension of both
      arguments, and the dimension of the intersection; test that all three dimensions are the
      same (e.g., all are Polygons).
      
      Add tests for all MBR* functions for various combinations of shapes, lines and points.
      47cce188
  7. 02 Mar, 2007 1 commit
  8. 21 Feb, 2007 1 commit
  9. 12 Feb, 2007 1 commit
  10. 07 Dec, 2006 2 commits
  11. 06 Dec, 2006 1 commit
  12. 18 Jul, 2006 1 commit
    • jimw@rama.(none)'s avatar
      Bug #19498: Inconsistent support for DEFAULT in TEXT columns · d18eacc7
      jimw@rama.(none) authored
        When a default of '' was specified for TEXT/BLOB columns, the specification
        was silently ignored. This is presumably to be nice to applications (or
        people) who generate their column definitions in a not-very-clever fashion.
      
        For clarity, doing this now results in a warning, or an error in strict
        mode.
      d18eacc7
  13. 05 Jul, 2006 1 commit
  14. 04 Jul, 2006 1 commit
  15. 27 Jun, 2006 1 commit
  16. 22 Jun, 2006 1 commit
  17. 02 Mar, 2006 1 commit
    • anozdrin@mysql.com's avatar
      Implementation of WL#2897: Complete definer support in the stored routines. · fbb59203
      anozdrin@mysql.com authored
      The idea is to add DEFINER-clause in CREATE PROCEDURE and CREATE FUNCTION
      statements. Almost all support of definer in stored routines had been already
      done before this patch.
      
      NOTE: this patch changes behaviour of dumping stored routines in mysqldump.
      Before this patch, mysqldump did not dump DEFINER-clause for stored routines
      and this was documented behaviour. In order to get full information about stored
      routines, one should have dumped mysql.proc table. This patch changes this
      behaviour, so that DEFINER-clause is dumped.
      
      Since DEFINER-clause is not supported in CREATE PROCEDURE | FUNCTION statements
      before this patch, the clause is covered by additional version-specific comments.
      fbb59203
  18. 01 Nov, 2005 1 commit
  19. 15 Oct, 2005 1 commit
  20. 26 Sep, 2005 1 commit
  21. 21 Sep, 2005 1 commit
  22. 27 Aug, 2005 1 commit
  23. 10 Aug, 2005 1 commit
  24. 05 Aug, 2005 1 commit
  25. 29 Apr, 2005 1 commit
  26. 10 Dec, 2004 1 commit
  27. 22 Oct, 2004 1 commit
  28. 02 Oct, 2004 1 commit
    • monty@mishka.local's avatar
      More fixes for strict mode: · be4ca46f
      monty@mishka.local authored
      More tests.
      Better error messages.
      Fixed bug when checking if we updated all needed columns for INSERT.
      Give an error if we encounter a wrong float value during parsing.
      Don't print DEFAULT for columns without a default value in SHOW CREATE/SHOW FIELDS.
      Fixed UPDATE IGNORE when using STRICT mode.
      be4ca46f
  29. 24 Sep, 2004 1 commit
  30. 22 Sep, 2004 1 commit
  31. 15 Sep, 2004 1 commit
  32. 26 Aug, 2004 1 commit
  33. 20 Jul, 2004 1 commit
  34. 13 May, 2004 1 commit
  35. 17 Mar, 2004 1 commit
  36. 16 Mar, 2004 1 commit
  37. 04 Mar, 2004 1 commit
  38. 06 Nov, 2003 1 commit
  39. 02 Jun, 2003 1 commit