Ticket #1263 (new enhancement)
TableContainer: Proper datasource implementation for JDBC connected SQL tables
| Reported by: | Joonas Lehtinen | Owned by: | Joonas Lehtinen |
|---|---|---|---|
| Priority: | undefined | Milestone: | IT Mill Sponsored Backlog |
| Component: | undefined | Version: | |
| Keywords: | Cc: | ||
| Known Issue description: | |||
| Hours estimate: | 150 | Deadline (dd.mm.yyyy): | |
| Known Issue version (since): | Known Issue title: | ||
| Hours done: | Depends to: | ||
| Affects documentation: | no | ||
| Known Issue workaround: | |||
| Affects release notes: | yes | Contract: | |
Description
Abstract goal
Design Container -implementation that would make creating simple JDBC-based applications like Workhours a lot easier. If possible, eliminate the most SQL from the Java-code as well as copying between containers.
Probably including
- Most functionality currently in QueryContainer?
- Inserting new rows to database
- Updating rows in database
- Proper handling of transactions
- Proper handling of database connections
- Sortable
Change History
Note: See
TracTickets for help on using
tickets.
