Description:
Adding a "point" column to a MyISAM table makes the row_format dynamic. Since the point
column always takes 25 bytes, the row_format should be able to be "fixed".
The documentation for the spatial column types is pretty sparse, too...
How to repeat:
CREATE TABLE `ask_test` (
`id` int(10) unsigned NOT NULL,
`geo` point NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1
mysql> show table status like 'ask_te%'\G
*************************** 1. row ***************************
Name: ask_test
Engine: MyISAM
Version: 10
Row_format: Dynamic
Rows: 0
Avg_row_length: 0
Data_length: 0
Max_data_length: 281474976710655
Index_length: 1024
Data_free: 0
Auto_increment: NULL
Create_time: 2006-10-24 02:40:28
Update_time: 2006-10-24 02:40:28
Check_time: NULL
Collation: latin1_swedish_ci
Checksum: NULL
Create_options:
Comment:
1 row in set (0.00 sec)
Suggested fix:
let the row_format be "fixed" even with a "point" column.
Description: Adding a "point" column to a MyISAM table makes the row_format dynamic. Since the point column always takes 25 bytes, the row_format should be able to be "fixed". The documentation for the spatial column types is pretty sparse, too... How to repeat: CREATE TABLE `ask_test` ( `id` int(10) unsigned NOT NULL, `geo` point NOT NULL ) ENGINE=MyISAM DEFAULT CHARSET=latin1 mysql> show table status like 'ask_te%'\G *************************** 1. row *************************** Name: ask_test Engine: MyISAM Version: 10 Row_format: Dynamic Rows: 0 Avg_row_length: 0 Data_length: 0 Max_data_length: 281474976710655 Index_length: 1024 Data_free: 0 Auto_increment: NULL Create_time: 2006-10-24 02:40:28 Update_time: 2006-10-24 02:40:28 Check_time: NULL Collation: latin1_swedish_ci Checksum: NULL Create_options: Comment: 1 row in set (0.00 sec) Suggested fix: let the row_format be "fixed" even with a "point" column.