This should be okay - I just tried it from scratch and it works, with the
following expected tables in my region's mysql db
+--------------------------+
| Tables_in_opensimregions |
+--------------------------+
| estate_groups |
| estate_managers |
| estate_map |
| estate_settings |
| estate_users |
| estateban |
| land |
| landaccesslist |
| migrations |
| primitems |
| prims |
| primshapes |
| regionban |
| regionenvironment |
| regionextra |
| regionsettings |
| regionwindlight |
| spawn_points |
| terrain |
+--------------------------+
where robust and the region use separate databases. Perhaps you still have a
config gremlin somewhere?
On 02/10/12 00:26, Nicky Perian wrote:
maybe this is a non-problem but, it has me stumped.
when running a standalone w/mysql the estate tables are populated into the
database.
when running robust/opensim instances the estate tables appear to to be placed
in an sqlite database
as per the setting in GridCommon.ini of:
[DatabaseService]
;
; ### Choose the DB
;
; SQLite
Include-Storage = "config-include/storage/SQLiteStandalone.ini";
Attempts to comment this out and use mysql database fail w/ region not part of
estate error.
Is there a way to place the estate tables into the mysql database?
This came up because I wanted to transfer ownership of region by table entry as
I had done before in a standalone
configuration.
If this is the way estate data is handled in the robust/opensim configuration;
how are the estate tables edited to
transfer region ownership?
Additionally, the show names data does not persist for run to run which it does
for a standalone.
Comments please.
Nicky
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
