You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2007/09/06 16:04:31 UTC
[jira] Created: (JCR-1116) Database persistence managers: log
database and driver name and version
Database persistence managers: log database and driver name and version
-----------------------------------------------------------------------
Key: JCR-1116
URL: https://issues.apache.org/jira/browse/JCR-1116
Project: Jackrabbit
Issue Type: Improvement
Components: core
Reporter: Thomas Mueller
Assignee: Thomas Mueller
Priority: Minor
Database related problems can be solved more easily when we know what database and driver version is used. Sometimes multiple database drivers are installed in an app server environment, and the user may not even know it.
Currently the driver class name is logged. I suggest to log the driver and database name and version as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1116) Database persistence managers: log
database and driver name and version
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1116:
-------------------------------
Fix Version/s: 1.3.4
Merged (with adaptations for JCR-940/JCR-1400) to the 1.3 branch in revision 631379.
> Database persistence managers: log database and driver name and version
> -----------------------------------------------------------------------
>
> Key: JCR-1116
> URL: https://issues.apache.org/jira/browse/JCR-1116
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 1.3.4, 1.4
>
>
> Database related problems can be solved more easily when we know what database and driver version is used. Sometimes multiple database drivers are installed in an app server environment, and the user may not even know it.
> Currently the driver class name is logged. I suggest to log the driver and database name and version as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1116) Database persistence managers: log
database and driver name and version
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller resolved JCR-1116.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.4
Revision 573272: Log the driver and database name and version. Also log a warning when using an older Oracle version with the newer Oracle persistence manager.
> Database persistence managers: log database and driver name and version
> -----------------------------------------------------------------------
>
> Key: JCR-1116
> URL: https://issues.apache.org/jira/browse/JCR-1116
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 1.4
>
>
> Database related problems can be solved more easily when we know what database and driver version is used. Sometimes multiple database drivers are installed in an app server environment, and the user may not even know it.
> Currently the driver class name is logged. I suggest to log the driver and database name and version as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.