The migrations table is the one that keeps information about which
migrations have been run. So if you run migrations once over a data
resource table (useraccounts or any other) the last migration number
will be stored, and migration will not happen again.
I don't recommend dropping the migrations table entirely -- that's
calling for trouble. When migrations go wrong for whatever reason, I
recommend deleting only the row in the migrations table that corresponds
to the data resource in question -- in this case the UserAccount row in
that table. Leave the other rows alone.
Master_Mirage wrote:
Sub Notes:
We did try 1st to drop just 'useracounts' table and re-launch robust and
opensim.exe. It didnot see the table was gone and loaded completly anyway.
It did not make a new one.
Next (after putting the orginal table back) Droped the migrations table. It
did see it wasent there and redid just the migrations table but not fix
usersacounts table (problem remained the same).
We had to drop both tables at the same time then it did remake both
correctly and used the orginal un-touched 'user' table data.
-----
Our New Web Page
Http://www.TritonGrid.com
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
