[
https://issues.apache.org/jira/browse/DERBY-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635240#comment-13635240
]
Mike Matrigali commented on DERBY-6128:
---------------------------------------
Dag what kind of errors and in what situations will users using past releases.
What does a user do if they run into problems?
And does soft vs. hard upgrade come into play?
Also can this change be backported, or does it cause problems if a user takes a
new release but then wants to downgrade back
to the older release within the version (ie. takes a 10.10.2 with a fix, but
then wants to go back to 10.10.1).
I've marked that this issue needs a release note, so that we warn users.
> Examine Derby classes to determine if we need to add serialVersionUID to any
> of them
> ------------------------------------------------------------------------------------
>
> Key: DERBY-6128
> URL: https://issues.apache.org/jira/browse/DERBY-6128
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Reporter: Rick Hillegas
> Fix For: 10.11.0.0
>
> Attachments: derby-6128-ecpds40.diff, SerializableLister.java
>
>
> The discussion on DERBY-6124 has raised the possibility that we may need to
> add serialVersionUIDs to some serializable Derby classes. Without the
> serialVersionUIDs, Derby may encounter deserialization errors on objects
> which were serialized by one version of Derby or the JVM and then
> deserialized by another version of Derby or the JVM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
