✳flâneur — a map of the web's best reading

Don't Do This - PostgreSQL wiki

wiki.postgresql.org · 3,822 words · saved by 1 readers

SQL_ASCII means "no conversions" for the purpose of all encoding conversion functions. That is to say, the original bytes are simply treated as being in the new encoding, subject to validity checks, without any regard for what they mean. Unless extreme care is taken, an SQL_ASCII database will usually end up storing a mixture of many different encodings with no way to recover the original characters reliably. If your input data is already in a hopeless mixture of unlabelled encodings, such as IRC channel logs or non-MIME-compliant emails, then SQL_ASCII might be useful as a last resort—but consider using bytea first instead, or whether you could autodetect UTF8 and assume non-UTF8 data is in some specific encoding such as WIN1252. Don't use psql -W or psql --password. Using the --password or -W flags will tell psql to prompt you for a password, before trying to connect to the server - so you'll be prompted for a password even if the server doesn't require one. It's never required, as i

Don't Do This - PostgreSQL wiki Want to edit, but don't see an edit button when logged in? Click here. Don't Do This From PostgreSQL wiki Jump to navigation Jump to search Contents 1 Database Encoding 1.1 Don't use SQL_ASCII 1.1.1 Why not? 1.1.2 When should you? 2 Tool usage 2.1 Don't use psql -W or --password 2.1.1 Why not? 2.1.2 When should you? 2.2 Don't use rules 2.2.1 Why not? 2.2.2 When should you? 2.3 Don't use table inheritance 2.3.1 Why not? 2.3.2 When should you? 3 SQL constructs 3.1 Don't use NOT IN 3.1.1 Why not? 3.1.2 When should you? 3.2 Don't use upper case table or column names

Explore this link on the map →

related reading