This is a known issue with MySQL. The problem is the value of the
property storing the information has been dimensioned too small. This
will be fixed in the 2.1 release. For now change the type of property
value to text. Like this:
CREATE TABLE PROPERTIES (
VERSION_ID bigint NOT NULL,
PROPERTY_NAMESPACE varchar(50) NOT NULL,
PROPERTY_NAME varchar(50) NOT NULL,
PROPERTY_VALUE text NOT NULL,
PROPERTY_TYPE varchar(50) NOT NULL,
IS_PROTECTED tinyint(1) NOT NULL,
PRIMARY KEY (VERSION_ID,PROPERTY_NAMESPACE,PROPERTY_NAME)
) TYPE=InnoDB;
Oliver
kranga wrote:
Using MySQL as the store, I've run into what looks like a serious error. I
created 6 versions of a given file. I stopped tomcat and started it and the
reportMethod() started failing with an Internal Server Error. After some
investigation, I see that the property_value field of the properties table
holds 255 characters and the version-set property maxes that out when v1.4
is created! Is this a bug or am I doing something wrong? It works as long as
I don't shutdown tomcat. Am I shutting down tomcat wrong?
Has anyone else run into the same problem?
-Thanks
Karthik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
