Hi,

 

  We're building an online application system and are running into a problem with SQL Server's 8060 character limit for a single row in a table, i.e. if you try and do an update query that happens to attempt to add characters that push the row over the 8060 character limit, SQL Server throws an exception.  Which is a little annoying to unknowing users who simply are trying to answer the question asked of them on the application…

 

  I noticed on the tips and tricks page (http://castor.exolab.org/tips-tricks.html) a reference to relational inheritance that might help me, but I wanted to ask specifically.

 

  (Disclaimer: Please don't judge me for the implementation--it is inherited. J ) 

 

Details:

 

The situation is we have an object called "MyApplication" that contains a very large number of String properties each representing a question (er, answer rather) and maps to MyTable. 

 

There are multiple pages that represent the whole of the application (like a wizard).  The questions are of the nature that a person might have 500-1000 characters in answer.  As each page is posted, the MyApplication object is retrieved, the appropriate new information copied into the object, and then it is committed. 

 

The first several pages go along fine, but once they try to post a page that pushes the row in MyTable over 8060 characters, SQLServer's driver returns an exception complaining that the row cannot exceed 8060 chars.  

 

What I'd like to do (besides breaking up MyApplication into multiple objects, which is really quite impractical given rewrite that would be necessary) is tell castor to simply save these group of fields to table MyApplicationA and these group of fields to MyApplicationB and these others to MyApplicationC.  All would have the same key, and would be properly aggregated into one MyApplication java object, and thus transparent to my application.

 

So my question is: does relational inheritance do this for me?

 

thanks,

 

ken.

Reply via email to