are multiple messages in a second and that is usually (in my experience) meaning
the logging itself is slowing down the program. Leaving the unsuccesful message
as we need to know about that path.
Fixed all NHibernate unit tests by implementing missing persistency
methods, tables, columns and fixing bugs in the existing implementation.
Two minor changes to classes outside NHibernate module: Added Scene
instantiation for SceneObjectGroup in OpenSim.Data.Tests.BasicRegionTest
as this was required by the NHibernate persistency. In the process added
also mock constructor to Scene which only populates RegionInfo in the scene
which is used by ScenePart.RegionUUID. NHibernate module is still in
experimental state and has not been tested at opensim region or ugaim runtime
configuration. Adding unit tests to build is not yet advisable nor using
NHibernate module in any production setup.
NHibernate MySQL migration was not working as mysql dialect is
MySQL5Dialect now instead of MySQLDialect which is the migration
sub folder name. Fixed this by adding simple dialect to migration
sub type mapping to manager initialization to avoid need of renaming
migration script folder each time MySQL version changes. Removed
shared session and changed session to be constructed per call as
NHibernate session is not thread safe. Refactored manager member
names to be according to the naming convention (full words in camel case).
Enable users to enable only selected methods out of the
available set of remote methods to restrict remote
functionality to less harmful methods, such as
admin_broadcast, or admin_region_query.
Solves the problem of unable to load prim items on region start in MSSQL.
The error was in the MSSQLRegionData code that loads objects from the database,
due to reliance on the ParentID field that is not used.
* Must compare user region with previous calling of the same method to determine if we should look the user up.
* The first time, the previous region handle will be 0, so therefore it'll use the cached version.
* The second time, previousRegionHandle will be what we looked up on the first round
* The third time, it'll say.. we tried to deliver it once with or without lookup, we tried to deliver it a second time with lookup, and failed both times so end!