Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m migrating my app from MySQL to Postgres. If I do a rake db:schema:load, it loads fine into Postgres, and all my tests pass.
If I do rake db:migrate:reset, then an integer column that I had previously set to have :limit => 1 is set to have :limit => 2.
My migration sets it like so:
t.integer "foo", :limit => 1, :null => false
Is it simply a matter of Postgres having a lower minimum size?
The
smallinttype in PostgreSQL occupies two byte and accepts numbers from -32768 to +32767.There is no
tinyintlike in MySQL that occupies 1 byte and accepts numbers from -128 to 127.