action #1383
closeddatabase schema overhaul
Description
the database schema needs an overhaul. For example the name needs to be split up in separate fields for distro, version, build etc.
Updated by alarrosa about 10 years ago
- Target version deleted (
Sprint 02) - Estimated time set to 20.00 h
Updated by ancorgs about 10 years ago
As suggested in the last meeting, we should add t_created and t_updated columns to every table.
http://search.cpan.org/~ribasushi/DBIx-Class-TimeStamp-0.14/
Updated by lnussel about 10 years ago
ancorgs wrote:
As suggested in the last meeting, we should add t_created and t_updated columns to every table.
http://search.cpan.org/~ribasushi/DBIx-Class-TimeStamp-0.14/
Is it better to do that in perl or let the database do it?
http://stackoverflow.com/questions/1964233/does-sqlite3-support-a-trigger-to-automatically-update-an-updated-on-datetime
Updated by lnussel about 10 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
rename stopped to cancelled
Updated by lnussel about 10 years ago
- Due date set to 2014-02-18
- Start date changed from 2014-02-04 to 2014-02-10
- % Done changed from 10 to 30
- move all timestamps to t_* format
- add new fields to db schema
- add more info to perl db schema to allow deploy from perl
- fixed testsuite
- pushed
Updated by lnussel about 10 years ago
switch completely to perl based database deployment, tools/db.sql is no longer needed.
Updated by lnussel about 10 years ago
- % Done changed from 30 to 70
- use db based list view
- switched most controllers to id based selection
liveview is currently broken and still TODO
Updated by lnussel about 10 years ago
- Status changed from In Progress to Resolved
- % Done changed from 70 to 100
I think this task can be considered done for now.