Search Mailing List Archives
[protege-discussion] data too long for column 'long_value' at row1 in the protege 3.4 rc 2
tudorache at stanford.edu
Tue Mar 17 11:27:42 PDT 2009
I moved this discussion on the mailing list. Please post messages on the
mailing list, not directly to the developers, as others may be
interested in the topic. Thanks!
Please send the exact exception that you get in the console.
In 3.4, if a value has to be stored in the long_value column, then you
do not need any kind of special setting, because the long_value column
can store up to 16.777.215 characters. So something else must be wrong
in your setup. That is why the exact text of the exception might help.
When you run using the API (not the GUI), it is possible that another
protege.properties is used, not the one that is used in the Protege UI.
If you want to override or set the value of a protege property, you can
use the call:
sunweicong85 at gmail.com wrote:
> Thanks very much for your reply! I have tried the way you say,but it did not work . In my ontology,the length of content of the peoperty RDFS:Comment in some datas is more than 500 chars(about 800), so the protege api will change the location to save from the short_value into the long_value, and then the error comes out: data too long for column 'long_value' at row1. But that shouldn't happen by what you say,because the length of the long_value is so long.
> But I find a interesting thing, I set the protege.properties: Database.typename.short.value.type.com.mysql.jdbc.Driver=VARCHAR(1000) COLLATE UTF8_GENERAL_CI,and then I succeed by the protege but not the api . Then what I should do is to succeed by the api, and the problem confuses me for many days!
> Thank you !
> Tania Tudorache wrote:
>> First fix is to remove all the lines for setting the column types from
>> the protege.properties file (like the one you mention below). This was
>> necessary in the 3.4 beta, but not in the 3.4 release.
>> By default now, Protege uses columns that are 500 chars long (for frame,
>> slot, facet and short_value), and for the 'long_value' column it uses a
>> "MEDIUMTEXT" which is quite long (16.777.215 characters).
>> If after cleaning up the protege.properties file, you still get the
>> exception, please post the entire exception to the list.
>> There is a way to set the long_value column type in 3.4, if the above
>> solution fails.
>> sunweicong85 at gmail.com wrote:
>>> when i save the owl file into the mysql database,the following error
>>> comes out: data too long for column 'long_value' at row1. i use the
>>> protege 3.4 rc 2. i find the information how to deal the problem in 3.4
>>> beta ,by adding a line in protege.properties:
>>> Database.typename.varchar.com.mysql.jdbc.Driver=VARCHAR(255) COLLATE
>>> ,but the way is applied in the 3.4 rc 2. how i should do ?
>>> thank you !
>>> protege-owl mailing list
>>> protege-owl at lists.stanford.edu
>>> Instructions for unsubscribing:
>> protege-owl mailing list
>> protege-owl at lists.stanford.edu
>> Instructions for unsubscribing:
> Quoted from:
More information about the protege-discussion