Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] data too long for column 'long_value' at row1 in the protege 3.4 rc 2

Tania Tudorache tudorache at stanford.edu
Mon Mar 16 16:27:35 PDT 2009


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.

Tania


sunweicong85 at gmail.com wrote:
> Hi,all!
>     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 
> UTF8_BIN 
> ,but the way is applied in the 3.4 rc 2. how i should do ?
>        thank you !
>                                                                                        sun
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>
>   




More information about the protege-owl mailing list