Actions
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.
Actions
Added by lnussel about 10 years ago. Updated about 10 years ago.
Description
the database schema needs an overhaul. For example the name needs to be split up in separate fields for distro, version, build etc.
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/
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
rename stopped to cancelled
switch completely to perl based database deployment, tools/db.sql is no longer needed.
liveview is currently broken and still TODO
I think this task can be considered done for now.