This issue needs investigation - ideally, if a quick fix and upgrade task can be made, it should be done immediately.

The below limits developer's abilities to serialize objects via Xstream and store them in propertyset - the column for text is restricted (see below).

This is also, obviously, a generic problem for retrieving and storing large amounts of data on a property.

> Basically, the Hibernate provider for PropertySet uses the same column
> (a VARCHAR(255)) for both string and text properties. So we'll either
> need to fix PropertySet, or write our own provider that does a better job.
>
> C

Also, IFF this issue impacts existing meta-data an upgrade task will have to be written.

For the fix, is it as simple as:

• writing a new PropertySet.hbm.xml which uses a long text field (using
  our clob type)
• writing an upgrade task to move the existing data across to that new
  field?