| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
in mysql, mssql and sqlite database plugins
|
| |
|
|
|
|
|
|
| |
moved/created/deleted to match version numbers cached by viewers.
This is done in the way that one would expect (e.g. moving a folder increments version number on both source and destination parent folders).
This should hopefully improve viewer reuse of its cached inventory information.
Currently MySQL only but will be implement for SQLite/MSSQL if there are no issues.
|
| |
|
|
|
|
|
|
| |
Delete(string[], string[]) call (not just string, string).
This is to stop viewer inventory cache version numbers becoming out of sync with grid stored numbers when viewer performs these actions.
If there are no problems with these changes, they will be propogated to SQLite (and MSSQL if that's simple enough).
May also need to do the same on folder store/create/delete and maybe propogate version increments up the folder hierarchy, but that requires investigation.
|
| |
|
|
| |
Not doing this was allowing the viewer inventory cache to become out of sync if an item was directly deleted.
|
| |
|
|
|
|
|
| |
If these links are not deleted, then they will build up in the player's inventory until they can no longer log in.
Accidental deletion of links due to bugs or other causes is potentially inconvenient but on a par with items being
accidentally moved. When a link is deleted, the target of the link is never touched.
This is a general solution that accounts for the use of links anywhere in the user's inventory.
|
| |
|
|
|
|
| |
Revert "Allow item links to be deleted even when other deletes and purges are disabled."
This reverts commit 491279f99afc65860d44765ee7829c7dd5e4e38e.
|
| |
|
|
|
|
|
| |
If these links are not deleted, then they will build up in the player's inventory until they can no longer log in.
Accidental deletion of links due to bugs or other causes is potentially inconvenient but on a par with items being
accidentally moved. When a link is deleted, the target of the link is never touched.
This is a general solution that accounts for the use of links anywhere in the user's inventory.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
for avatar->avatar
|
| | |
|
| |
|
|
| |
This should accommodate various timeout problems that exist with the current connection pool code in a more general and standard way.
|
| | |
|
| |
|
