Auto_migrations does not like :timestamp
Reported by toulmean | November 9th, 2007 @ 02:20 AM
Fields defined as :timestamp do not live well with db:auto:migrate.
They are compared to the database, which presents the field as datetime.
Rails converts timestamp fields into datetime fields:
http://jacqueschirag.wordpress.c...
The rake task throws an error about the invalid default value. I don't know why the default value is set to ''.
** Execute db:auto:migrate
-- change_column("us_hits", :timestamp, :timestamp)
rake aborted!
Mysql::Error: Invalid default value for 'timestamp': ALTER TABLE us_hits CHANGE timestamp timestamp datetime DEFAULT ''
Here is the table definition:
create_table "us_hits", :force => true do |t|
t.column "timestamp", :timestamp
end
Comments and changes to this ticket
-
-
Chris Wanstrath November 9th, 2007 @ 08:54 AM
- Assigned user changed from “Chris Wanstrath” to “PJ Hyett”
- State changed from “new” to “open”
-
toulmean November 12th, 2007 @ 02:36 AM
This might just be a reflection of a bug in Rails:
http://dev.rubyonrails.org/ticke...
It looks like this is fixed in 1.2.5.
Not auto_migrations responsibility in any case.
Closing this bug.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
PJ Hyett
toulmean