[WG: Sakai QA] [Building Sakai] [Deploying Sakai] Is anybody storing resource bodies in database?
jimeng at umich.edu
Wed Apr 22 04:40:19 PDT 2009
So far we know of at least two sakai instances running in pilot/
production with database storage of content bodies in tables that use
BINARY_ENTITY serialization. One needs immediate conversion to
filesystem storage and the other is never expected to convert from
I have created a JIRA ticket outlining the problem:
Conversion to storage of content bodies in filesystem fails for
BINARY_ENTITY serialized resources
On Apr 22, 2009, at 5:59 AM, Steve Swinsburg wrote:
> Hi Jim,
> A production environment I administer stores its content in a
> clustered Oracle database. We have had no production issues with
> this setup and the DB is offsite. It's been around for a while and
> was upgraded from 2.4 to 2.5.x. The conversion from XML to binary
> took place then so we are using BINARY_ENTITY serialization. There
> is no capacity to change this setup, for various reasons.
> Steve Swinsburg
> Portal Systems Developer
> Centre for e-Science
> Lancaster University
> LA1 4YT
> email: s.swinsburg at lancaster.ac.uk
> phone: +44 (0) 1524 594870
> On 22 Apr 2009, at 04:45, Jim Eng wrote:
>> This is a very important question. It's not an immediate crisis, but
>> we may need information in planning for how to help you convert to
>> filesystem storage of resource bodies at some point. Here are my
>> If you think you might be running sakai in production or pilot using
>> database storage of resource bodies, please reply to this email.
>> Please also tell us what version of sakai you are running. If you
>> running 2.5 or later, are you using BINARY_ENTITY or XML
>> of resources.
>> I believe that Sakai out of the box is configured to store resource
>> bodies as BLOB's in a database table , I believe, but that is not
>> recommended for production.
>> If you think you might be using database storage of content bodies in
>> pilot or production and you're unsure of how to answer the other
>> questions, please reply and we will help figure out what needs to be
>> production mailing list
>> production at collab.sakaiproject.org
>> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
More information about the sakai-qa