Move Telehub tables and data from EstateSettings to RegionSettings.

This is damage control es EstateSettings is not the place this can be put.
EstateSettings is nt unique to a region and therefore would introduce
a hard limit of one telehub per estate, completely shutting off the
option of having SL style telehubs, e.g. one per region. Whole
estate teleport routing can still be implemented id desiresd, this
way all options are open while the other way most options get closed
off.

1 files changed, 0 insertions, 21 deletions

diff --git a/OpenSim/Data/MySQL/Resources/EstateStore.migrations b/OpenSim/Data/MySQL/Resources/EstateStore.migrations
index 591295b..df82a2e 100644
--- a/OpenSim/Data/MySQL/Resources/EstateStore.migrations
+++ b/OpenSim/Data/MySQL/Resources/EstateStore.migrations
@@ -78,25 +78,4 @@ ALTER TABLE estate_settings AUTO_INCREMENT = 100;
 COMMIT;
 
 
-:VERSION 33         #--------------------- ( Supporting Telehubs
 
-BEGIN;
-CREATE TABLE IF NOT EXISTS `spawn_points` (
-  `EstateID` varchar(36) COLLATE utf8_unicode_ci NOT NULL,
-  `PointX` float NOT NULL,
-  `PointY` float NOT NULL,
-  `PointZ` float NOT NULL,
-  KEY `EstateID` (`EstateID`)
-) ENGINE=Innodb;
-
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubObject` varchar(36) NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubName` varchar(255) NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubEnabled` tinyint(4) NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubPosX` float NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubPosY` float NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubPosZ` float NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubRotX` float NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubRotY` float NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubRotZ` float NOT NULL;
-ALTER TABLE `estate_settings` ADD COLUMN `TelehubRotW` float NOT NULL;
-COMMIT;
\ No newline at end of file