db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: Enforcing length restrictions for streams of unknown length
Date Wed, 02 Aug 2006 18:05:12 GMT


Mike Matrigali wrote:
> This may or may not work, not sure.  Here is stuff to be aware of.
> If you do this approach, the store will go ahead and insert and log data 
> into the database.  For it to work correctly you will
> have to make sure that the resulting error from the limit at least
> aborts the statement which is doing the insert/update.
> 
> My guess is that you are going to get some sort of STORE exception
> with the limit exception wrapped below it.  I would not be surprised
> if the current store exception is more severe than you want it to
> be as the current code does not expect this error - you may have
> to define a new less severe error in this case.  There may be more
> than one exception path.  Make sure to test the case where
> the inserted blob exceeds the page size and the case where the
> inserted blob is less than the page size. 

By severity I meant that store may currently raise a transaction or
system level exception.  A good test would be to have a multi-statement
transaction and make sure this error does not back out an earlier 
statement in the uncommitted transation.


Mime
View raw message