Creating timestamp fields instead of time type for postgres

[jwaldner]

Hello! Thank you so much for your interest in Pop. The fact you care enough to be here, right now, helping makes us very happy.

Delete the above section and the instructions in the sections below before submitting.

Description

this is the migration up

create_table("children") {
t.Column("id","integer", {primary: true})
t.Column("first_name", "string", {})
t.Column("last_name", "string", {})
t.Column("birth_date", "timestamp", { })
t.Column("image", "blob", {})
}

create_table("check_ins") {
t.Column("child_id", "int")
t.Column("checkin_id", "date")
t.PrimaryKey("child_id", "checkin_id")

t.Column("first_in", "time", {})
t.Column("first_out", "time", {})

}

Steps to Reproduce the Problem

migration up

Expected Behavior

time fields for first_in & first_out
What did you what to happen? Tell us a story. We love to read.

Actual Behavior

timestamp & timestampz
In the happiest of happy places what should have happened?

Info

pop 6.0.1

Please precise your OS, the Pop version and if you're using Pop through Buffalo.

Just now found a work around, use "time " in the field type instead of "time"