Ah!  Ok.  Then perhaps 1/1/1970 would be just as suitable and less confusing?

From: Victor Lowther [mailto:notifications@github.com]
Sent: Sunday, October 06, 2013 9:52 AM
To: crowbar/barclamp-crowbar
Cc: Hirschfeld, Rob
Subject: Re: [barclamp-crowbar] CB 2.0: Switch to Postgres for production, and refactor the provisioner BC to hook it back into the node lifecycle. [1/3] (#720)


In crowbar_framework/db/migrate/20120731225405_create_barclamps.rb:

>        t.string     :source_path,               :null=>true

>        t.integer    :layout,                    :default=>2

>        t.string     :requirements,              :null=>true

>        t.string     :members,                   :null=>true

>        t.string     :commit,                    :null=>true, :default=>'unknown'

> -      t.date       :build_on,                  :null=>true, :default=>'unknown'

> +      t.datetime   :build_on,                  :null=>true, :default=>Time.now
On Sun, Oct 6, 2013 at 9:05 AM, Rob Hirschfeld <notifications@github.com<mailto:notifications@github.com>>wrote: In crowbar_framework/db/migrate/20120731225405_create_barclamps.rb: > t.string :source_path, :null=>true > t.integer :layout, :default=>2 > t.string :requirements, :null=>true > t.string :members, :null=>true > t.string :commit, :null=>true, :default=>'unknown' > - t.date :build_on, :null=>true, :default=>'unknown' > + t.datetime :build_on, :null=>true, :default=>Time.now this was supposed to be a build time value - if should be unknown if it's not provided.
well, 'unknown' does not parse to a date, and postgres is very strict about that sort of thing.
…
— Reply to this email directly or view it on GitHub<https://github.com/crowbar/barclamp-crowbar/pull/720/files#r6786855> .

—
Reply to this email directly or view it on GitHub<https://github.com/crowbar/barclamp-crowbar/pull/720/files#r6786941>.