Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008065opensim[REGION] OpenSim Corepublic2016-11-24 05:452016-11-24 14:26
Assigned To 
PlatformPCOSWindowsOS Version10
Product Versionmaster (dev code) 
Target Versionmaster (dev code)Fixed in Version 
Summary0008065: [ASSET DB]: MySQL failure creating asset ... Error: Data too long for column 'description' at row 1
DescriptionI spotted some errors on the consoles for the Openvue grid using dev master while an OSGrid avatar was visiting via hypergrid. The console indicated that the creation of some DB assets that look like they may be landmarks were throwing errors. I am not sure what the visiting avatar saw as an error or asset creation message... but it may be a mismatch in the "description" field length allowed by OSGrid and the default set in dev master.

OpenSim.exe console:
13:23:36 - [Assets]: Upload failed: aa1b4295-5d5b-4154-a00d-8f603b2f9b25 type 3 will retry later
13:23:36 - [Assets]: Upload failed: f32ce319-89e9-4d92-9e1a-e8f540647e9f type 3 will retry later

Robust.exe console:
12:23:35 - [ASSET DB]: MySQL failure creating asset aa1b4295-5d5b-4154-a00d-8f603b2f9b25 with name "HG Openvue Welcome Island". Error: Data too long for column 'description' at row 1
12:23:35 - [ASSET DB]: MySQL failure creating asset f32ce319-89e9-4d92-9e1a-e8f540647e9f with name "Okaloosa Island". Error: Data too long for column 'description' at row 1

Both sets of messages are then repeated several times on the retries.

One thing that is surprising is that its an error rather than the description being shortened to fit the available DB field "description" length.

But also, my investigation indicates that we may still have serious issues with the asset table field length for "description" which is still 64 characters long in the latest MySQL DB settings in dev master... though I thought it had been lengthened before to 128 characters.

I occasionally still see some yellow warnings (but not red errors) indicating trimming of description fields down to 64 characters, and a check of the Openvue grid MyQQL database tables indicates that the Asset description length is set to varchar(64).

I thought this had been corrected and the description field lengthened to 128 characters before? See [^] [^]

But on checking now I see the description field is still set at length 64 on Openvue as a dev master grid with no manual changes to the data bases other than the usual migrations taking place.

As reported some years ago, we know that 64 characters is far too short for some uses of the description field to hold URLs and data for things like Google spreadsheet avatar visitor trackers, where the URL definitely exceeds 64.... and if trimmed cannot work. Its also incompatible with Second Life decsription n field length, so scripts working there that use the description field will not work in the same way.
Additional InformationOpenSim/Data/MySQL/Resources/AssetStore.migrations:

# -----------------


  `name` varchar(64) NOT NULL,
  `description` varchar(64) NOT NULL,
  `assetType` tinyint(4) NOT NULL,
  `local` tinyint(1) NOT NULL,
  `temporary` tinyint(1) NOT NULL,
  `data` longblob NOT NULL,
  `id` char(36) NOT NULL DEFAULT '00000000-0000-0000-0000-000000000000',
  `create_time` int(11) DEFAULT '0',
  `access_time` int(11) DEFAULT '0',
  `asset_flags` int(11) NOT NULL DEFAULT '0',
  `CreatorID` varchar(128) NOT NULL DEFAULT '',
  PRIMARY KEY (`id`)

TagsNo tags attached.
Git Revision or version number
Run Mode Grid (Multiple Regions per Sim)
Physics EngineBulletSim
Script Engine
Environment.NET / Windows64
Mono VersionNone
Attached Files

- Relationships
related to 0007476closedBlueWall Prim descirptions truncated to 64 bytes 
related to 0007350new MySQL Data Base Schemas - Inconsistency in Name and Description Field Lengths 

-  Notes
UbitUmarov (administrator)
2016-11-24 06:58

My BAD, asset description size limit back to 64
aiaustin (developer)
2016-11-24 07:06
edited on: 2016-11-24 07:57

Hang on Ubit, you have amended the internal checks on length to the SHORTER (incorrect?) 64 character limit. Surely the change needs to be to the migrations to the data field lengths to make them be 127 (is that right?)

Are all data bases supported going to be changed? I see SQLite, MySQL and PGSQL changed. but what of FSAssets?

One other question Ubit... you say that "this field will possible go away in future"... do you mean the Asset "description" field? Is this because the real" used description is in the prims and primitems.. where the description field length is varchar(255) and the "assets" description is not actually in use?

UbitUmarov (administrator)
2016-11-24 11:20

yes my mistake was forgetting that assets description is sill only there for compatibility with possible external modules using it.
reverted to 64 so no other changes are needed.
inventory items description is used and has a large limit.(127)
prims have their own storage for description with limit of 255
apparently sl and viewers now also limit to 127 on prims, so may need to review that
aiaustin (developer)
2016-11-24 14:26

Thanks for the explanation. Good the store error rather than trimming is now fixed. Thanks.

- Issue History
Date Modified Username Field Change
2016-11-24 05:45 aiaustin New Issue
2016-11-24 05:45 aiaustin Relationship added related to 0007476
2016-11-24 05:54 aiaustin Description Updated View Revisions
2016-11-24 05:55 aiaustin Description Updated View Revisions
2016-11-24 05:55 aiaustin Relationship added related to 0007350
2016-11-24 06:58 UbitUmarov Note Added: 0031298
2016-11-24 07:06 aiaustin Note Added: 0031299
2016-11-24 07:07 aiaustin Note Edited: 0031299 View Revisions
2016-11-24 07:57 aiaustin Note Edited: 0031299 View Revisions
2016-11-24 07:57 aiaustin Note Edited: 0031299 View Revisions
2016-11-24 11:20 UbitUmarov Note Added: 0031300
2016-11-24 14:26 aiaustin Note Added: 0031301

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker