| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| | |
Replaced all NNN_StoreName.sql migration resources with a more
readable, single-file-per-store
|
| | |
| |
| |
| |
| | |
Uses MySqlScript class to correctly run proc/func definitions
that need delimiter change. Requires MySql.Data.dll 6.2 or later.
|
| |/
|
|
|
|
|
|
|
|
| |
Scans for migration resources in either old-style "scattered" (one file per version)
or new-style "integrated" format (single file "Resources/{StoreName}.migrations[.nnn]") with ":VERSION nnn" sections).
In the new-style migrations it also recognizes ':GO' separators for parts of the SQL script
that must be sent to the server separately. The old-style migrations are loaded each in one piece
and don't support the ':GO' feature.
Status: TESTED and works fine in all modes!
|
| | |
|
| |
|
|
| |
statements. Fixed here.
|
| |
|
|
|
|
| |
stored in regionsettings. Upon generation of a new tile image, the old one is deleted. Tested for SQLite and MySql standalone.
* Fixed small bug with map search where the local sim regions weren't found.
|
| | |
|
| |
|
|
| |
asset deletion in robust handler.
|
| |
|
|
|
|
|
| |
CHANGES THE ASSET SERVER PROTOCOL and means you CAN NOT MIX PRIOR VERSIONS
WITH LATER ONES. It may also eat your babies, yada, yada, yada.
The usual cautions for migrations to the assets table apply.
Coding: Can not guarantee nut free.
|
| | |
|
| |
|
|
|
|
| |
home and position info in the presence service. WARNING: I violated a taboo by deleting 2 migration files and simplifying the original table creation for Presence. This should not cause any problems to anyone, though. Things will work with the new simplified table, as well as with the previous contrived one. If there are any problems, solving them is as easy as dropping the presence table and deleting its row in the migrations table. The presence info only exists during a user's session anyway.
BTW, the Meshing files want to be committed too -- EOFs.
|
| |
|
|
| |
inside a transaction.
|
| | |
|
| | |
|
| |
|
|
| |
for avatar->avatar
|
| |
|
|
| |
there for now, in case bugs pop up with XInventory.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
This ensures that 'cmd' gets disposed on errors
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
| |
this seems the least evil way forward since mono 2.6 and later will see increasing usage, and this only works with what was SQLiteNG
MAC USERS WILL NEED TO CHANGE REFERENCES TO "OpenSim.Data.SQLite.dll" to "OpenSim.Data.SQLiteLegacy.dll" in OpenSim.ini and config-include/StandaloneCommon.ini (if using standalone)
See the OpenSim.ini.example and StandaloneCommon.ini.example files for more details
This commit also temporarily changes unsigned ParentEstateID values in the OpenSim.Data.Tests to signed temporarily, since the new plugin enforces creation of signed fields in the database (which is what the SQL actually specifies). And change data columns in sqlite is a pita.
|
| |
|
|
| |
it wasn't working because of debug work that I'd forgotton to take out
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
| |
with it rather than within the loop
disposing of it within the loop causes Mono.Data.Sqlite.dll to get upset, and it's the wrong behaviour anyway
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| | |
updating the Migrations table will not occur in a partial transaction, which
would be auto-rolled-back later.
|
| | |
| |
| |
| |
| |
| | |
Include the library so that Windows builds correctly
It appears that Windows is okay with either SQLite or SQLiteNG
Incorporate the latest fixes made by Diva to OpenSim.Data.SQLite
|
| |/
|
|
| |
shortly be changed to work under mono 2.6 and above
|
| | |
|
| | |
|
| |
|
|
| |
changes in IUserAccountService, just the data layer.
|
| |
|
|
| |
statements.
|
| |
|
|
| |
some magic numbers with libomv enums
|
| |
|
|
| |
64-bit machines (no SQLite).
|
| |
|
|
|
| |
This allows scripts to set WindLight parameters for clients connecting
to a region. Currently, this is only supported by the Meta7 viewer.
|
| |
|
|
| |
won't fix the bug I'm seeing with regions not realizing they are already part of an estate, but it will fix the OpenSim crash if that situation ever comes up
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
of a region and joining it to an existing estate or creating a new estate,
as well as creating an estate owner if in standalone, and assigning estate
owners. In Grid mode, existing users must be used. MySQL ONLY!!!! so far, as
I can't develop or test for either SQLite or MSSQL.
|
| |
|
|
|
|
|
|
| |
to start estates at 100. Existing databases having autcreated estates below
100 will see a gap in estate numbering. Other database implementors need to
ensure that no estates with numbers less that 100 are autocreated, unless
they are prepared to deal with the viewer's built-in notions of
Linden Mainland
|
| |
|
|
|
| |
defaults. Adding code to facilitate estate creation / managemment as part of
first time start up
|
| | |
|
| |
|
|
|
|
| |
placeholder added.
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
| |
for it. GridUserService makes more sense; it's the user of the grid, "grid user". I changed it everywhere.
|
| |
|
|
|
| |
this will initially store home location data instead of the presence service
compiles but not enough to actually test yet
|
| |
|
|
|
|
|
|
| |
been removed from Data.Null.NullPresenceData
Unfortunately, this meant publicly exposing the underlying service for the connector.
The other solution would be to create alternative initializers for services and connectors where objects could be given directly rather than loaded indirectly through config.
Unfortunately, this would require a lot of work in this case but might be the better way forward.
|
