Forum OpenACS Q&A: Consequences of changing sec_session_properties.property_value to clob/blob
to stuff too large a value into the
sec_session_properties.property_value field. What would be the
danger of converting this field to a blob or a clob (in Oracle--sorry
I don't know the corresponding field in PG)?
It looks like there are only a few places this is accessed
I'm still not clear on how the .xql files work, and recall that some
magic must be done when using bind variables to insert blob/clob
values into Oracle...
I've been wanting to visit this issue myself. clob storage isn't the most efficient thing in the world ... we could pull the old trick of putting strings <= 4000K in length into the existing varchar and longer strings into a clob. This would fix the APM problem (where you can't install all packages at once). I don't know of any other place where this has been a problem, the table's really defined to be used for passing around small chunks of stuff.