On 17 November 2011 02:32, Josh Berkus <j...@agliodbs.com> wrote: > >> (I'm a bit concerned about the angle that the code has some smarts >> currently about where to put hyphens in output. If we rip that out >> it could definitely break application code, whereas dropping a check >> shouldn't.) > > Right. Do we need to dump the hyphen logic?
Only if you think that it's better to have something that covers many cases but is basically broke. Perhaps it's different for code that is already committed, but in the case of new submissions it tends to be better to have something that is limited in a well-understood way rather than less limited in a way that is unpredictable or difficult to reason about. -- Peter Geoghegan http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
