3 ms·
Aaaahhhhh ... rails developers. I take your point. As to CHAR vs VARCHAR -- well, is it fixed length or constantly changing? The clue is in the name. And CHAR
by Craiggybear 15y ago
Aaaahhhhh ... rails developers. I take your point.
As to CHAR vs VARCHAR -- well, is it fixed length or constantly changing? The clue is in the name. And CHAR is usually up to 50% faster on overhead and VARCHAR uses padding which can be a huge waste of space. They should just know this.
Then, SQL Joins are plain English and should be easily visualised in the abstract (it does help if you can see the data in front of you though, I can't deny).
Date vs Time is something I am finding confuses lots of people. Precision as well.
- Skalman 15y agoRegarding CHAR/VARCHAR: At least in MySQL VARCHAR only has one byte of padding, while CHAR is a huge waste of space if you don't use mostly full-length strings. Edit: http://dev.mysql.com/doc/refman/5.6/en/char.html http://dev.mysql.com/doc/refman/5.6/en/char.html
- Erwin 15y agoWell, that's database dependent -- for Postgres there's no real performance difference: http://wiki.postgresql.org/wiki/FAQ#What_is_the_difference_between_the_various_character_types.3F http://wiki.postgresql.org/wiki/FAQ#What_is_the_difference_b... It's CHAR that pads with spaces, not VARCHAR.