[deepamehta-devel] [Bug #14438] CM corrupted in RC4

[admin at berlios.de]

Bug #14438, was updated on 2008-Sep-01 19:10
Here is a current snapshot of the bug.

Project: DeepaMehta
Category: Storage Layer
Status: Open
Resolution: None
Bug Group: None
Priority: 7
Submitted by: x28
Assigned to : jri
Summary: CM corrupted in RC4

Details: I experienced a similar severe error as #13628 fixed in RC4: 
After I erroneously pasted text into the NAME field rather than into the description field, this text was duplicated into ALL name fields, description fields, and obviously also into workspace properties, leading to the error message "There are 3 default workspaces, only tt-workspace-1 "administration" is considered".
The offending text contained CGI URLs, double quotes  and TWO single apostrophes. The text was truncated at the second single apostrophe and concluded by a backslash.
(Although I have come to install separate instances for each group of maps --much like one ppt deck for several mindmapping slides-- I lost several hours of work. And since "1 Unglueck kommt selten allein", I deleted the geometry of the recovered map by hitting Delete All next to delete!)

Follow-Ups:

Date: 2008-Sep-03 17:57
By: jri

Comment:
I'm very sorry about your data loss.

For the moment I've no explanation for that. The escaping issue in DB queries (regarding quotes and so on) should be solved since we use prepared statements. Although the storage layer is not yet completely transformed to prepared statements, the statements in question (setting topic name and properties) are so. I checked it meanwhile.

Perhaps the problem originates from an overflow because of the quite long topic name. For the length of the topic name there is a limit of 255 charachters. Your offending text has 301 charachters. (BTW: there is virtually no limit for property values, but practically there is a 64K limit with the client/server scenario.) I'll investigate the problem and will fix this bug soon.

I guess you use the standalone DeepaMehta (as opposed to client/server) with HSQL-DB, Right?

Thank you very much for reporting this crucial bug. Future users will benefit substantially. Regarding you, nothing remains to me but repeating my deep excuse.

Jörg

-------------------------------------------------------

Date: 2008-Sep-01 19:16
By: x28

Comment:
Since I don't know how to attach files here: this is the offendig text:

imagine if you will, an internet where you don’t start your 
experience by “googling.”
http://www.petechen.com/wp/%3Fm%3D200807%26paged%3D2

the who has always been a way to get at the what
http://www.downes.ca/cgi-bin/page.cgi?post=45723
Twitter'S Move Towards Semantic Info and the Content Graph
-------------------------------------------------------

For detailed info, follow this link:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=14438&group_id=5174