For me the reason to do so is a physical limitation of the Unify database, whose absolute limit to CHAR type fields is 255. Unify is more braindead than that: it doesn't even know about VARCHAR type fields (read this, page 125). If you need longer than 255, you'll have to use TEXT (no length) or BINARY (no length). Fortunately, dealing with CLOB/BLOB's in Unify is exceptionally easy.
All databases suck. One way or another :)
In reply to Re: [OT] Database row width and cargo cult programming
by Tux
in thread [OT] Database row width and cargo cult programming
by moritz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |