Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • scriptorium scriptorium
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • degrowth
  • scriptoriumscriptorium
  • Merge requests
  • !23

Merged
Created Dec 08, 2019 by Ponder Stibbons@ponderOwner

Fix #199, fix migrations

  • Overview 5
  • Commits 4
  • Changes 2

Deleted migration that was renaming and dropping user columns, the columns were changed in an earlier migration or created with the correct name.

Adjusted the changing of the datatype of the "conferences:day_start" and "conferences:day_end" columns. PostgreSQL did not know how to convert a time into an integer, and because of that refused to change the type. To be database independent, I did not use the PostgreSQL way by explaining how to convert with USING CAST(EXTRACT(hour from :day_start) AS integer). I chose to create a new column, drop the old one and rename the new column to the old name.

Edited Dec 09, 2019 by Ponder Stibbons
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix_199