News for hackers. Stuff that matters.
Re:PostgreSQL Exercises by mattmanser on Thursday December 12, 2013 @05:08PM (#6897633)
Most people don't bother with them, it's like juggling namespaces, mainly a complete waste of keystrokes.

There's little to no chance of collisions but you have to use them constantly, which is annoying. Few benefits, lots of downsides.

Re:PostgreSQL Exercises by AlisdairO on Friday December 13, 2013 @03:22PM (#6902688)
I don't think it's just about collisions, in fairness. There's also the aspect of managing user permissions by schema, searching for tables, and so on.

Obviously this only becomes super-useful in pretty sizeable projects, but I tend to consider using schemas a good habit to be in.

Re:PostgreSQL Exercises by asdasf on Monday December 16, 2013 @10:35AM (#6915313)
Have you ever tried using them before? You can set your search path, you don't need to type out schema.table. Your objects are already in a schema anyways, it isn't like you type out public.table all the time. What are these "lots of downsides" you leave unspecified? And how do they outweigh the benefits of grouping database objects together for both namespacing and permissions purposes?