| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Coz on one box they defaulted to utfmb3, which .NET doesn't support.
|
| |
|
|
|
|
|
| |
InnoDB -> MyISAM
utf8
if not exists
white space
|
| |
|
|
| |
operation is very expensive
|
| |
|
|
|
|
| |
XAssetStore db tables
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| |
|
|
|
|
| |
XAssetStore db tables"
This reverts commit e520364f65e1915e13d28b829e9dd62f6904957d.
|
| |
|
|
|
|
| |
XAssetStore db tables
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| |
|
|
|
|
|
|
| |
capitalized like Avatars, Friends, etc.
Also fixes access time being set on assets rather than XAssetsMeta
This is to try and be somewhat consistent with other service tables that are mainly in this style.
No migration is supplied, since nobody should be using this service yet except on a test basis.
|
| |
|
|
|
|
|
| |
Some successful collision attacks have been carried out on sha1 with speculation that more are possible.
http://en.wikipedia.org/wiki/Cryptographic_hash_function#Cryptographic_hash_algorithms
No successful attacks have been shown on sha256, which makes it less likely that anybody will be able to engineer an asset hash collision in the future.
Tradeoff is more storage required for hashes, and more cpu to hash, though this is neglible compared to db operations and network access.
|
|
|
This is an extremely crude implemenation which almost works by accident. Nevertheless it does work.
It can be tested with the instructions at http://opensimulator.org/wiki/Feature_Proposals/Deduplicating_Asset_Service#Testing
It does not interact at all with the existing asset service or any data stored there.
This code is subject to change without notice and should not be used for anything other than gawking.
|
