Databases
StackOverflow2013
Postsdbo
POPerforming a heroku db:push gives ArgumentError: invalid date (Sequel::InvalidValue) is this something standard?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPerforming a heroku db:push gives ArgumentError: invalid date (Sequel::InvalidValue) is this something standard?
    text
    copied!<p>Performing a heroku db:push</p> <p>everything seem to be going ok </p> <p>Sending schema Schema: 100% |==========================================| Time: 00:00:05 Sending indexes schema_migrat: 100% |=====================================| Time: 00:00:00 users: 100% |==========================================================| Time: 00:00:01 histories: 100% |========================================================| Time: 00:00:00 Sending data 4 tables, 587 records </p> <p>schema_migrat: 100% |==============================================| Time: 00:00:00</p> <p>when i get</p> <p>/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/date.rb:1573:in <code>new_by_frags': ArgumentError: invalid date (Sequel::InvalidValue) from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/date.rb:1618:in</code>parse' from /Library/Ruby/Gems/1.8/gems/sequel-3.17.0/lib/sequel/core.rb:222:in <code>string_to_datetime' from /Library/Ruby/Gems/1.8/gems/sequel-3.17.0/lib/sequel/timezones.rb:92:in</code>convert_input_timestamp' from /Library/Ruby/Gems/1.8/gems/sequel-3.17.0/lib/sequel/timezones.rb:163:in <code>convert_timestamp' from /Library/Ruby/Gems/1.8/gems/sequel-3.17.0/lib/sequel/timezones.rb:46:in</code>database_to_application_timestamp'</p> <p><strong>EDIT: Adding Schema/Migration</strong> <Pre> t.string "apothiki" t.string "timh" t.datetime "created_at" t.datetime "updated_at" t.string "photo_file_name" t.string "photo_content_type" t.integer "photo_file_size" t.datetime "photo_updated_at" </pre></p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload