He is right that lots has been said about coding standards in other languages and even right out holy wars have been launched on the
subject, but as far as SQL goes, not quite enough has been said on the subject for us to have a great war to end all wars.
I was also happy to see that we agreed with all his points except his first one. Yes I felt dissed, and thought hmm
if someone as important as Josh thinks our aliases should be very descriptive and we should use the table name rather than
the alias where possible, surely there must be something wrong with me for not believing in this fundamental philosophy.
In the rest of this excerpt I shall make fun of Josh and also set forth some of our own SQL Coding guidelines. Hopefully
Josh won't take too much offense at this small jibe.
PostGIS 1.3.5 urgent upgrade if you are running 1.3.4
We were forced to release a 1.3.5 PostGIS upgrade as a result of a bug we accidentally introduced in 1.3.4 during our code cleanup.
We apologize for any inconvenience this may have caused people. This bug affects the use of MULTILINESTRINGS and rears its ugly head
by giving errors such as invalid circular line string when calling
ST_Multi or another odd error when doing a Force collection on a MULTILINESTRING. This hits mapserver users using these geometry types the hardest.