diff options
| author | holyfoot/hf@mysql.com/hfmain.(none) <> | 2007-11-13 10:51:47 +0400 |
|---|---|---|
| committer | holyfoot/hf@mysql.com/hfmain.(none) <> | 2007-11-13 10:51:47 +0400 |
| commit | 7d111abf0eb9efbdc46d2924c0f27d078252e4f5 (patch) | |
| tree | 7e2b4e01a21459d9a666cbdd1b2b399281a96c25 /sql/item_geofunc.cc | |
| parent | 29ea825e574aaeb3ebd3e02b44a105b26da899ec (diff) | |
| download | mariadb-git-7d111abf0eb9efbdc46d2924c0f27d078252e4f5.tar.gz | |
Bug #31158 Spatial, Union, LONGBLOB vs BLOB bug (crops data)
max_length parameter for BLOB-returning functions must be big enough
for any possible content. Otherwise the field created for a table
will be too small.
Diffstat (limited to 'sql/item_geofunc.cc')
| -rw-r--r-- | sql/item_geofunc.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/item_geofunc.cc b/sql/item_geofunc.cc index 6cb8c790319..7900396e5d8 100644 --- a/sql/item_geofunc.cc +++ b/sql/item_geofunc.cc @@ -29,7 +29,7 @@ void Item_geometry_func::fix_length_and_dec() { collation.set(&my_charset_bin); decimals=0; - max_length=MAX_BLOB_WIDTH; + max_length= max_field_size; maybe_null= 1; } |