Project

General

Profile

Actions

action #1383

closed

database schema overhaul

Added by lnussel over 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2014-02-10
Due date:
2014-02-18
% Done:

100%

Estimated time:
20.00 h

Description

the database schema needs an overhaul. For example the name needs to be split up in separate fields for distro, version, build etc.

Actions #1

Updated by ancorgs over 10 years ago

  • Target version set to Sprint 02
Actions #2

Updated by alarrosa over 10 years ago

  • Target version deleted (Sprint 02)
  • Estimated time set to 20.00 h
Actions #3

Updated by alarrosa over 10 years ago

  • Target version set to Sprint 02
Actions #4

Updated by alarrosa over 10 years ago

  • Assignee set to lnussel
Actions #5

Updated by ancorgs over 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/

Actions #6

Updated by lnussel over 10 years ago

  • Assignee changed from lnussel to aplanas
Actions #7

Updated by aplanas over 10 years ago

  • Assignee changed from aplanas to lnussel
Actions #8

Updated by lnussel over 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

Actions #9

Updated by lnussel over 10 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

rename stopped to cancelled

Actions #10

Updated by lnussel over 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
Actions #11

Updated by lnussel over 10 years ago

switch completely to perl based database deployment, tools/db.sql is no longer needed.

Actions #12

Updated by lnussel over 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

Actions #13

Updated by lnussel about 10 years ago

live view fixed

Actions #14

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.

Actions

Also available in: Atom PDF