On Tue, Sep 18, 2018 at 3:19 AM, Florian Ebeling
wrote:
> Is there a common practice how to apply migrations for staging systems
> running various feature branches?
>
> Assume there is a db of significant size, and feature branches including
> migrations are pushed to this server instance.
Can yo
> On Sep 18, 2018, at 6:19 AM, Florian Ebeling
> wrote:
>
> But how would you establish what to pass as `v` here from the new branch?
>
If you have run a migration up in staging, you can get its version from rake
db:migrate:status (but I'm pretty sure you knew that). Are you talking about
> On Sep 18, 2018, at 6:19 AM, Florian Ebeling
> wrote:
>
> Is there a common practice how to apply migrations for staging systems
> running various feature branches?
>
> Assume there is a db of significant size, and feature branches including
> migrations are pushed to this server instance
Is there a common practice how to apply migrations for staging systems
running various feature branches?
Assume there is a db of significant size, and feature branches including
migrations are pushed to this server instance.
Just calling `rake db:migrate` won't be enough, as often it will be th
On Tue, Sep 18, 2018 at 5:59 AM, Joe Guerra wrote:
> todaydate = Time.new
>
> todaydate = todaydate.year.to_s + "-" + todaydate.month.to_s + "-" +
> todaydate.day.to_s
>
> and the column for enddate is a date type.
Aside from the potential problem of redefining the same variable,
I'd avo
Hi, I defined time like this --->
require 'time'
todaydate = Time.new
todaydate = todaydate.year.to_s + "-" + todaydate.month.to_s + "-" +
todaydate.day.to_s
and the column for enddate is a date type. It had worked previously, I
just updated the dates in a populate rake file and s
6 matches
Mail list logo