Oliver Zeigermann wrote:
Hi Luke!
I am afraid you are right :( What about using a BLOB for the propterty values? This would mean certainly mean a slow down and would require changes to the DB adapter, but would work, right?
Oliver
Luke Noel-Storr wrote:
Hmm,
OK, yet further investigation has shown the problem to be with the properties table, the column type for the property_value column is varchar(255), so when the history-set is getting longer than this it is truncated and becomes invalid.
Some databases like PostgreSQL have a type TEXT with unlimited length. We only need to change the type in the schema, the DB adapter doesn't have to be changed. For databases that don't have a similar type, I guess a BLOB will be one way. Or we may want to store the data in a more compact way, like compressing or using a relation table. Some properties like history are a list of items. We may use the "type" column (I think there is one) in the properties table to do custom processing like extracting each item from another table.
Carlos
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
