You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/09/19 16:57:24 UTC
[jira] Updated: (DERBY-1318) Add an upgrade test to verify that
DataSources can be serialized by the previous release and then correctly
deserialized by the current release
[ http://issues.apache.org/jira/browse/DERBY-1318?page=all ]
Rick Hillegas updated DERBY-1318:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.0.
> Add an upgrade test to verify that DataSources can be serialized by the previous release and then correctly deserialized by the current release
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1318
> URL: http://issues.apache.org/jira/browse/DERBY-1318
> Project: Derby
> Issue Type: Test
> Components: JDBC, Test
> Affects Versions: 10.2.1.0
> Reporter: Rick Hillegas
> Fix For: 10.2.2.0
>
>
> Currently, our DataSources are serializable in order to play well with JNDI. However, we have no upgrade test verifying that DataSource serialization works across release boundaries. We should add this case to our upgrade tests.
> Further recommendations by Dan:
> "I do think though that upgrade testing recently brought into the mainline by Deepa should be enhanced to test:
> - serializing Derby''s data source implementations in 10.1 and seeing it unserializes with 10.2
> (maybe into a BLOB column)
> - making a Reference object out of Derby''s data source implementations in 10.1 and making it into
> an object with 10.2. (if this type of tetsing makes sense for References')"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira