Varchar 256 why

Conversion Between Date and Time Types. The Geometry Class Hierarchy. GeometryCollection Class. MultiLineString Class. Supported Spatial Data Formats. Geometry Well-Formedness and Validity. Spatial Reference System Support. Creating Spatial Columns. Populating Spatial Columns. Optimizing Spatial Analysis. Creating Spatial Indexes. Data Type Storage Requirements. Choosing the Right Type for a Column.

InnoDB Cluster. Some of us old-timers use varchar [or that newfangled nvarchar ] mostly for historic reasons. The young-bloods tend to be using varchar [though I even wonder about the logic of that].

Assuming you are trying to come up with a "rule of thumb" for character fields for values such as "description", what practice do you tend to prescribe? Gene Wirchenko. Post by Thomas Kellerer Post by greg. Now, however, you can go up to 65, characters on VARCHAR, so if you're still using "" then that seems arbitrary and not well thought out or your schema is just old.

That's not totally true. Using a varchar of or less saves one byte vs one over So if you don't know any particular size to use, is reasonable. So there is no reason to artificially use a smaller value. That's not true either.