Comments on: Rails Migration Data Types http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/ So I don't have to figure things out more than once. Thu, 28 Aug 2008 09:40:54 +0000 http://wordpress.org/?v=2.6.1 By: ynw http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-16966 ynw Sun, 08 Jun 2008 02:43:10 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-16966 <p>Informations in this post is outdated</p> Informations in this post is outdated

]]> By: SEO G http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-11684 SEO G Fri, 07 Mar 2008 02:23:16 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-11684 <p>Using Rails 2.0 in the default migrations file it uses t.timestamps and it automatically creates the columns created_at and updated_at (both datetime in MySQL). I guess since so many people wanted to have those columns for most models they rolled it into the standard migrations file when you generate the model file.</p> <p>Michael</p> Using Rails 2.0 in the default migrations file it uses t.timestamps and it automatically creates the columns created_at and updated_at (both datetime in MySQL). I guess since so many people wanted to have those columns for most models they rolled it into the standard migrations file when you generate the model file.

Michael

]]> By: Noah Magram http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-10771 Noah Magram Mon, 11 Feb 2008 23:34:29 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-10771 <p>A TIMESTAMP column in many RDBMSes gets set automagically on every row insert, some on every update. It can also be set explicitly in an INSERT or UPDATE statement.</p> <p>It also appears that rails' :binary really does mean BLOB, not BINARY - so much for convention there.</p> A TIMESTAMP column in many RDBMSes gets set automagically on every row insert, some on every update. It can also be set explicitly in an INSERT or UPDATE statement.

It also appears that rails’ :binary really does mean BLOB, not BINARY - so much for convention there.

]]> By: Michael Deck http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-6804 Michael Deck Mon, 19 Nov 2007 18:01:08 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-6804 <p>Migration data types are just aliases for the column types supported by the underlying database. So the answer to your question "what's the difference between datetime and timestamp" is that it depends on which RDBMS you're using. In MySql there is no difference, both map to datetime. In Sybase however they map to datetime and timestamp respectivly. In Oracle all of the date types (date, time, datetime, timestamp) all map to the date type.</p> <p>The <em>Agile Web Development with Rails</em> book has a nice chart that defines the mapping from migration type to db column type for all of the major databases. The chart is in chapter 16, pg 267 of my version of the book.</p> Migration data types are just aliases for the column types supported by the underlying database. So the answer to your question “what’s the difference between datetime and timestamp” is that it depends on which RDBMS you’re using. In MySql there is no difference, both map to datetime. In Sybase however they map to datetime and timestamp respectivly. In Oracle all of the date types (date, time, datetime, timestamp) all map to the date type.

The Agile Web Development with Rails book has a nice chart that defines the mapping from migration type to db column type for all of the major databases. The chart is in chapter 16, pg 267 of my version of the book.

]]> By: Chrononaut http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-1446 Chrononaut Mon, 05 Mar 2007 18:36:20 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-1446 <p>Timestamps require half the space of a datetime to store, because they are based on unixtime. Therefore they also have a smaller range (1970-2050 or something).</p> Timestamps require half the space of a datetime to store, because they are based on unixtime. Therefore they also have a smaller range (1970-2050 or something).

]]> By: From Journeyman to Master » Archives » Computer science? What? http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-1156 From Journeyman to Master » Archives » Computer science? What? Tue, 20 Feb 2007 00:45:05 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-1156 <p>[...] came across this blog post when I googled rails data type. Below is part of the [...]</p> [...] came across this blog post when I googled rails data type. Below is part of the [...]

]]> By: Simon http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-897 Simon Wed, 14 Feb 2007 14:22:19 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-897 <p>Trey:</p> <p>When you say binary being 0s and 1s, what you are saying is that binary is represented by 0s and 1s in machine language. Then everything in every software is represented by 0s and 1s. Boolean, on the other hand, is represented by 0 or 1 in programming language. That 0 or 1 in turn is represented by a bunch of 0s and 1s.</p> Trey:

When you say binary being 0s and 1s, what you are saying is that binary is represented by 0s and 1s in machine language. Then everything in every software is represented by 0s and 1s. Boolean, on the other hand, is represented by 0 or 1 in programming language. That 0 or 1 in turn is represented by a bunch of 0s and 1s.

]]> By: kofno http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-790 kofno Thu, 08 Feb 2007 19:35:45 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-790 <p>I think :decimal is also supported with :precision and :scale options.</p> I think :decimal is also supported with :precision and :scale options.

]]> By: Tiago Pinto http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-673 Tiago Pinto Fri, 19 Jan 2007 18:37:37 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-673 <p>Unless I'm completely wrong and accordingly to what I can remember, I think <em>timestamp</em> includes something related to unix timestamp (like fractions of seconds or something).</p> Unless I’m completely wrong and accordingly to what I can remember, I think timestamp includes something related to unix timestamp (like fractions of seconds or something).

]]> By: Jake Dust http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-222 Jake Dust Sat, 23 Dec 2006 16:54:07 +0000 http://solutions.treypiepmeier.com/2006/12/04/rails-migration-data-types/#comment-222 <p>Datetime includes year; Timestamp doesn't. That's all the difference, as far as I remember.</p> Datetime includes year; Timestamp doesn’t. That’s all the difference, as far as I remember.

]]>