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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2009/06/03 09:22:07 UTC
[jira] Commented: (DERBY-4254) If upgrade is not performed when
connecting with the upgrade=true atribute is specified, Derby should
produce a warning
[ https://issues.apache.org/jira/browse/DERBY-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715844#action_12715844 ]
Knut Anders Hatlen commented on DERBY-4254:
-------------------------------------------
It would be nice if we could make it even more general and get a warning for every connection attribute that was ignored (e.g., attributes for re-encrypting a database and misspelled attributes).
> If upgrade is not performed when connecting with the upgrade=true atribute is specified, Derby should produce a warning
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4254
> URL: https://issues.apache.org/jira/browse/DERBY-4254
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Affects Versions: 10.6.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> If a database is already booted in soft upgrade mode upgrade=true has no effect if a new connection is made. Derby should issue a warning on the connection if this occurs. See derby-user thread:
> http://www.nabble.com/Hard-upgrade-failing--td23826558.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.