Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
mdspatial_createdb.sh | 2020-05-11 | 299 Bytes | |
mdspatial_load.sh | 2020-05-11 | 460 Bytes | |
mdspatial_opclass_methods.sql | 2020-05-11 | 10.0 kB | |
mdspatial_types.sql | 2020-05-11 | 14.1 kB | |
README | 2020-05-11 | 1.1 kB | |
Totals: 5 Items | 25.9 kB | 0 |
MdSpatial.1.0 Shell and SQL Scripts ===================== mdspatial_load.sh - this script installs the MdSpatial opague types and associated methods in a database mdspatial_createdb.sh - this script will delete then recreate an Informix database mdspatial_types.sql - this SQL script creates MdSpatial opague types mdspatial_opclass_methods.sql - this script creates methods and an "opclass" to support Rtree indexing of the opague spatial types Notes: ====== the shell scripts are run as follows: sh <script> <database name> the SQL scripts are run from the "mdspatial_load.sh" script and produce text log files in /tmp. Caveats: ======== MdSpatial does NOT currently use nor require "blademgr". What this means is that if the prototype (signature in Informix parlance) of a method changes, there is no "nice" way to inform the DBMS. One of the above scripts will have to be modified and each database will have to be modified by hand - i.e. a "drop function" and then the (new) "create function" commands will have to be submitted to "dbaccess".