This should be read by almost all architects that I know. They cannot live without their tools. Sometimes during job interviews they keep on asking me not about knowledge, but about knowing one particular program for diagram writing.
Due to many questions about the PostgreSQL collation that were asked after my last short article about that, I decided to write some more about the current collation situation in PostgreSQL.
The collation setting is responsible for correct working functions such as
PostgreSQL is (IMHO) much better than MySQL but unfortunately it still lacks one of the greatest MySQL features: encoding.
Locale settings in MySQL are great. You can have different collation set for each database, table and even column (the same as it is in Interbase/Firebird). This gives the opportunity to simplify the database structure.
For example (I know, a very simplified example) when you have even a simple blog database and want to create a multilingual blog. Then it is enough to create one table for posts with two columns for body, each with different collation.
Python is a dynamically typed language. It basically means that you don’t have to declare exact types while declaring a variable. A very good and a very bad thing. As usually, there isn’t anything just good or just bad.