News for hackers. Stuff that matters.
Re:Database Design Mistakes by tracker1 on Saturday July 20, 2013 @09:00PM (#6077303)
CHAR/NCHAR are fixed length, VARCHAR/NVARCHAR are dynamic length... Usually the biggest restrictions to varchar/nvarchar are indexing limits.. generally my indexed fields for n/varchar will be 100 (email, name, etc) non-indexed, xml hashes, json will be NVARCHAR(MAX)/NTEXT when they aren't indexed.
Re:Database Design Mistakes by sehrope on Saturday July 20, 2013 @09:09PM (#6077337)
Yes but I see no point in using fixed length string fields. Double so for the examples the article gives (first and last names). All the times I've encountered them has been with legacy systems ands it's been a universal pain.

All your front end code ends up doing TRIM(...) to clean them up the extra padding. Modern RDBMSs all handle variable length fields efficiently so it's a waste of programmer time to have to deal with CHAR/NCHAR fields.