An error occurred fetching the project authors.
  1. 28 Apr, 2009 1 commit
    • Alexey Botchkov's avatar
      Bug#38990 Arbitrary data input plus GIS functions causes mysql server crash · d1968ad4
      Alexey Botchkov authored
         the Point() and Linestring() functions create WKB representation of an
         object instead of an real geometry object.
         That produced bugs when these were inserted into tables.
      
         GIS tests fixed accordingly.
                  
      per-file messages:
        mysql-test/r/gis-rtree.result
      Bug#38990 Arbitrary data input plus GIS functions causes mysql server crash 
          test result
        mysql-test/r/gis.result
      Bug#38990 Arbitrary data input plus GIS functions causes mysql server crash 
          test result
        mysql-test/t/gis-rtree.test
      Bug#38990 Arbitrary data input plus GIS functions causes mysql server crash 
          test fixed - GeomFromWKB invocations removed
        mysql-test/t/gis.test
      Bug#38990 Arbitrary data input plus GIS functions causes mysql server crash 
          test fixed - AsWKB invocations added
        sql/item_geofunc.cc
      Bug#38990 Arbitrary data input plus GIS functions causes mysql server crash 
           Point() and similar functions to create a proper object
      d1968ad4
  2. 15 Feb, 2009 1 commit
  3. 24 Nov, 2007 1 commit
  4. 20 Nov, 2007 1 commit
  5. 19 Nov, 2007 1 commit
    • holyfoot/hf@mysql.com/hfmain.(none)'s avatar
      Bug #30284 spatial key corruption. · 140dd4f3
      holyfoot/hf@mysql.com/hfmain.(none) authored
      SPATIAL key is fine actually, but the chk_key() function
      mistakenly returns error. It tries to compare checksums
      of btree and SPATIAL keys while the checksum for the SPATIAL isn't
      calculated (always 0). Same thing with FULLTEXT keys is handled
      using full_text_keys counter, so fixed by counting both
      SPATIAL and FULLTEXT keys in that counter.
      140dd4f3
  6. 13 Nov, 2007 1 commit
  7. 10 Oct, 2007 1 commit
    • gkodinov/kgeorge@magare.gmz's avatar
      Bug #30825: Problems when putting a non-spatial index on a GIS column · e971b18f
      gkodinov/kgeorge@magare.gmz authored
       Fixed the usage of spatial data (and Point in specific) with 
       non-spatial indexes.
       Several problems :
         - The length of the Point class was not updated to include the 
           spatial reference system identifier. Fixed by increasing with 4 
           bytes.
         - The storage length of the spatial columns was not accounting for
           the length that is prepended to it. Fixed by treating the 
           spatial data columns as blobs (and thus increasing the storage
           length)
         - When creating the key image for comparison in index read wrong
           key image was created (the one needed for and r-tree search,
           not the one for b-tree/other search). Fixed by treating the
           spatial data columns as blobs (and creating the correct kind of
           image based on the index type). 
      e971b18f
  8. 03 Oct, 2007 1 commit
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 02 Mar, 2007 1 commit
  15. 21 Feb, 2007 1 commit
  16. 12 Feb, 2007 1 commit
  17. 07 Dec, 2006 1 commit
  18. 06 Dec, 2006 1 commit
  19. 05 Jul, 2006 1 commit
  20. 04 Jul, 2006 1 commit
  21. 27 Jun, 2006 1 commit
  22. 22 Jun, 2006 1 commit
  23. 15 Oct, 2005 1 commit
  24. 26 Sep, 2005 1 commit
  25. 21 Sep, 2005 1 commit
  26. 27 Aug, 2005 1 commit
  27. 10 Aug, 2005 1 commit
  28. 05 Aug, 2005 1 commit
  29. 28 Jul, 2005 1 commit
  30. 29 Apr, 2005 1 commit
  31. 22 Oct, 2004 1 commit
  32. 22 Sep, 2004 1 commit
  33. 15 Sep, 2004 1 commit
  34. 26 Aug, 2004 1 commit
  35. 27 May, 2004 1 commit
  36. 17 Mar, 2004 1 commit
  37. 16 Mar, 2004 1 commit
  38. 04 Mar, 2004 1 commit
  39. 06 Nov, 2003 1 commit
  40. 03 Apr, 2003 1 commit