| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Dana Powers | Date: | August 21 2000 9:46pm |
| Subject: | RE: CHAR vs VARCHAR | ||
| View as plain text | |||
> Given this, what is the reason to use VARCHARs instead of CHARs? > > Given that the trailing spaces are removed when the value is retreived, I > can only see the case where you want to store strings with trailing spaces > as an instance where you would want to use VARCHAR. Storage. If you have a field such as email address that -could- be very long, but generally isnt, and is useless if truncated - you would need 255 chars. Unless you are willing to waste a majority of that space in the general case, you should use varchars. Dana > > >> The big difference is speed. CHARs are hella faster than > > VARCHARS. By a > > >> lot. CHARs take up a bit more disk space. It's disk space > > vs. speed. We > > >> choose speed for our applications.
| Thread | ||
|---|---|---|
| • CHAR vs VARCHAR | Claude Cormier | 21 Aug |
| • Re: CHAR vs VARCHAR | Rob McMillin | 21 Aug |
| • Re: CHAR vs VARCHAR | Claude Cormier | 21 Aug |
| • RE: CHAR vs VARCHAR | Sander Pilon | 21 Aug |
| • Re: CHAR vs VARCHAR | Kris Dahl | 21 Aug |
| • Re: CHAR vs VARCHAR | Jan Dvorak | 21 Aug |
| • Re: CHAR vs VARCHAR | Kris Dahl | 22 Aug |
| • Re: CHAR vs VARCHAR | Ed Wang | 21 Aug |
| • Re: CHAR vs VARCHAR | Kris Dahl | 21 Aug |
| • RE: CHAR vs VARCHAR | Christopher Thompson | 21 Aug |
| • RE: CHAR vs VARCHAR | Dana Powers | 21 Aug |
| • Re: CHAR vs VARCHAR | Steve Ruby | 21 Aug |
| • Fastest way to select sets | Christopher Thompson | 21 Aug |
| • Re: Fastest way to select sets | Steve Ruby | 22 Aug |
| • Re: Fastest way to select sets | Tonu Samuel | 22 Aug |
| • Re: Fastest way to select sets | Tino Hendricks | 28 Aug |
| • Re: Fastest way to select sets | Tonu Samuel | 2 Sep |
| • Re: CHAR vs VARCHAR | Paul Schmidt | 22 Aug |
