Task #2692 (closed)
Opened 9 years ago
Closed 9 years ago
Introduce SqlAction for all uses of JdbcTemplate
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.3 |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | 2010-12-09 (1) |
Description
The use of JDBC is spread throughout the code base, making refactoring and revising the SQL statements extremely difficult. All direct access to the database needs to be unified.
Change History (6)
comment:1 Changed 9 years ago by jmoore
- Milestone changed from OMERO-Beta4.2.1 to Unscheduled
comment:2 Changed 9 years ago by jmoore
comment:3 Changed 9 years ago by jmoore
Referencing ticket #2684 has changed sprint.
comment:4 Changed 9 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4.3
comment:5 Changed 9 years ago by jmoore
- Sprint set to 2010-12-09 (21)
comment:6 Changed 9 years ago by jmoore
- Remaining Time changed from 0.5 to 0
- Resolution set to fixed
- Status changed from new to closed
SqlAction introduced with 2 initial implementations. These subclass from the abstract SqlAction$Impl to reuse as much code as possible (refactoring needed). The strategy is that a default properties files (common/resources/ome/util/actions/default.properties) contains all SQL which is invariant. Dialects which need to vary from those values add a new properties files (common/resources/ome/util/actions/${omero.db.profile}.properties) and take the values from there.
(code commit waiting on release of 4.2.2)
Referencing ticket #2684 has changed sprint.