An error occurred fetching the project authors.
- 20 Sep, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
added get_field_default_value() function which obtains default value from the field (used in store_create_info() & get_schema_column_record() functions)
-
- 05 Jul, 2007 1 commit
-
-
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).
-
- 07 Jun, 2007 1 commit
-
-
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.
-
- 28 Mar, 2007 1 commit
-
-
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).
-
- 26 Mar, 2007 1 commit
-
-
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.
-
- 23 Mar, 2007 1 commit
-
-
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.
-
- 02 Mar, 2007 1 commit
-
-
Item_func_geometry_from_text::val_str() should set null_value in case of wrong data.
-
- 21 Feb, 2007 1 commit
-
-
Having maybe_null flag unset for geometry/spatial functions leads to wrong Item_func_isnull::val_int()'s results. Fix: set maybe_null flag and add is_null() methods.
-
- 12 Feb, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
Some fields (GEOMETRY first of all) can't be handled properly in this case at all. So we return an error in this case
-
- 07 Dec, 2006 2 commits
-
-
holyfoot/hf@mysql.com/deer.(none) authored
-
holyfoot/hf@mysql.com/deer.(none) authored
-
- 06 Dec, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
The problem is that the GEOMETRY NOT NULL can't automatically set any value as a default one. We always tried to complete LOAD DATA command even if there's not enough data in file. That doesn't work for GEOMETRY NOT NULL. Now Field_*::reset() returns an error sign and it's checked in mysql_load()
-
- 18 Jul, 2006 1 commit
-
-
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.
-
- 05 Jul, 2006 1 commit
-
-
ingo@mysql.com authored
-
- 04 Jul, 2006 1 commit
-
-
holyfoot@deer.(none) authored
we didn't have code creating GEOMETRY-type fields from Items (expression results) So i added this code
-
- 27 Jun, 2006 1 commit
-
-
holyfoot@deer.(none) authored
-
- 22 Jun, 2006 1 commit
-
-
holyfoot@deer.(none) authored
The AsBinary function returns VARCHAR data type with binary collation. It can cause problem for clients that treat that kind of data as different from BLOB type. So now AsBinary returns BLOB.
-
- 02 Mar, 2006 1 commit
-
-
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.
-
- 01 Nov, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 15 Oct, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 26 Sep, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 21 Sep, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 27 Aug, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 10 Aug, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 05 Aug, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 29 Apr, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 10 Dec, 2004 1 commit
-
-
gluh@gluh.mysql.r18.ru authored
mysqldump skips information_schema db 'use' now can use information_schema db changed value of column 'Null' to 'NO' if column is not nullable
-
- 22 Oct, 2004 1 commit
-
-
hf@deer.(none) authored
I learned that one shouldn't use String::set in val_str() methods...
-
- 02 Oct, 2004 1 commit
-
-
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.
-
- 24 Sep, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 22 Sep, 2004 1 commit
-
-
hf@deer.(none) authored
CREATE TABLE t1 SELECT POINT(1,2); fixed
-
- 15 Sep, 2004 1 commit
-
-
hf@deer.(none) authored
This bug is the result of weird error happening with mi_float8get and double arythmetic. I described that in 'Bug that looks potentially dangerous' email
-
- 26 Aug, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 20 Jul, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 13 May, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 17 Mar, 2004 1 commit
-
-
hf@deer.(none) authored
test for IGNORE added
-
- 16 Mar, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 04 Mar, 2004 1 commit
-
-
monty@mashka.mysql.fi authored
-
- 06 Nov, 2003 1 commit
-
-
bell@sanja.is.com.ua authored
code covarage for srid, GeomFromText with 2 parameters code covarage foe print() method of gis functions
-
- 02 Jun, 2003 1 commit
-
-
bar@bar.mysql.r18.ru authored
SHOW COLLATION columns have been removed: D -> Default C -> Compiled Y -> Yes
-