You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2014/10/14 18:48:34 UTC
[jira] [Issue Comment Deleted] (CLOUDSTACK-6835) db abstraction
layer in upgrade path
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Animesh Chaturvedi updated CLOUDSTACK-6835:
-------------------------------------------
Comment: was deleted
(was: BULK EDIT > Moving some of the recent created issues with fixVersion EMPTY to 4.5. These require further triage)
> db abstraction layer in upgrade path
> ------------------------------------
>
> Key: CLOUDSTACK-6835
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6835
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Rajani Karuturi
> Priority: Critical
> Fix For: 4.6.0
>
>
> about 198 of the issues reported by covery scan[1] on 26 May, 2014 are in the Upgrade###to###.java code
> and many of them related to Resource leaks and not closing the prepared statements.
> I think we should have a DB abstraction layer in the upgrade path so the the developer who needs to do select/insert/update data in the upgrade path need not write native sqls and worry about these recurring issues.
> [1] https://scan.coverity.com/projects/943
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)