ciccettino@stripped wrote:
> Hello,
> I'm a senior student at university of Roma 3; I'm doing a thesis aiming to provide a
> better sinergy between Grass and MySQL (using the
> fast all in memory engine); I found that heap engine doesn't support Gis Data because
> of the absence of Blob support, through which GIS
> data are, at the moment, stored. I also found that blob data aren't supported because
> memory engine has a fixed row format, which is
> incompatible with blobs.
[SNIP]
Hi,
This is not really an answer to your question, but an alternative route that you may want
to explore.
If you are after performance, instead of modifying the heap engine, you could use an
in-memory filesystem
to achieve your goal quickly and painlessly.
For example on a Linux OS, you could do the following:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 12G 4.1G 7.0G 38% /
devshm 506M 0 506M 0% /dev/shm
/dev/sda1 111G 85G 20G 81% /home
/dev/shm is the in-memory filesystem. To create a database there is straightforward:
$ mkdir /dev/shm/gis
$ ln -s /dev/shm/gis /usr/local/mysql/data/gis
$ mysql
mysql> use gis
mysql create table (... , b_fld blob, p_fld point) engine = myisam;
and then you have a fully functional MyISAM table in RAM.
Best regards
Giuseppe
--
Giuseppe Maxia, QA Developer
MySQL AB, www.mysql.com
