rubyonrailsin

On 22 March 2010 04:43, Mike Montagne <lists@ruby-forum.com> wrote:
> In the former, you're not even passing the information to the
> environment to build the tables you want. Of course then, it's critical
> to convey your intended design to deployment. A varchar(25) (intended
> field designation) requires 1/10th the disk resources that a string
> field (which translates to varchar(255)).

In the case of MySql I believe that the length of a varchar only
specifies the maximum length, it does not affect the actual space used
in the db as the data is stored as variable length records. I don't
know about postgresql.

Colin

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.