Re: PostgreSQL Developer Best Practices
От
John R Pierce
Тема
Re: PostgreSQL Developer Best Practices
Дата
Msg-id
55D8DD9B.7070302@hogranch.com
Ответ на
Re: PostgreSQL Developer Best Practices (Melvin Davidson)
Список
Дерево обсуждения
PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Karsten Hilbert <Karsten.Hilbert@gmx.net>
Re: PostgreSQL Developer Best Practices Ray Cote <rgacote@appropriatesolutions.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices Karsten Hilbert <Karsten.Hilbert@gmx.net>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Berend Tober <btober@computer.org>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices CaT <cat@zip.com.au>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Rob Sargent <robjsargent@gmail.com>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Rob Sargent <robjsargent@gmail.com>
Re: PostgreSQL Developer Best Practices "Joshua D. Drake" <jd@commandprompt.com>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices John R Pierce <pierce@hogranch.com>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices Jerry Sievers <gsievers19@comcast.net>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices rob stone <floriparob@gmail.com>
Re: PostgreSQL Developer Best Practices Allan Kamau <kamauallan@gmail.com>
Re: PostgreSQL Developer Best Practices Condor <condor@stz-bg.com>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices "Joshua D. Drake" <jd@commandprompt.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices Igor Neyman <ineyman@perceptron.com>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices "Daniel Verite" <daniel@manitou-mail.org>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices Adam Brusselback <adambrusselback@gmail.com>
Re: PostgreSQL Developer Best Practices "Karsten Hilbert" <Karsten.Hilbert@gmx.net>
Re: PostgreSQL Developer Best Practices CaT <cat@zip.com.au>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices John Turner <jjturner@energi.com>
Re: PostgreSQL Developer Best Practices "Joshua D. Drake" <jd@commandprompt.com>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices "Joshua D. Drake" <jd@commandprompt.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Adrian Klaver <adrian.klaver@aklaver.com>
Re: PostgreSQL Developer Best Practices "Joshua D. Drake" <jd@commandprompt.com>
Re: PostgreSQL Developer Best Practices John Turner <jjturner@energi.com>
Re: PostgreSQL Developer Best Practices John R Pierce <pierce@hogranch.com>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices Andy Colson <andy@squeakycode.net>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices John R Pierce <pierce@hogranch.com>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
Re: PostgreSQL Developer Best Practices "David G. Johnston" <david.g.johnston@gmail.com>
Re: PostgreSQL Developer Best Practices Thomas Kellerer <spam_eater@gmx.net>
Re: PostgreSQL Developer Best Practices Neil Tiffin <neilt@neiltiffin.com>
Re: PostgreSQL Developer Best Practices "Karsten Hilbert" <Karsten.Hilbert@gmx.net>
Re: PostgreSQL Developer Best Practices Neil Tiffin <neilt@neiltiffin.com>
Re: PostgreSQL Developer Best Practices John Turner <jjturner@energi.com>
Re: PostgreSQL Developer Best Practices Karsten Hilbert <Karsten.Hilbert@gmx.net>
Re: PostgreSQL Developer Best Practices Thomas Kellerer <spam_eater@gmx.net>
Re: PostgreSQL Developer Best Practices Melvin Davidson <melvin6925@gmail.com>
On 8/22/2015 12:40 PM, Melvin Davidson wrote: > What is occurring is that the developers are sending strings like 'Mr. > M\'vey', > which, if we set standard_conforming_strings = ON, would, and does, > result in errors and the statement failing, > which is a lot less desirable that a simple warning. if your developers were writing invalid C code (or whatever other language they program in), would you modify the compiler to accept their invalid syntax? or would you tell the developer to fix their code properly ? if the developers refused, why would you not fire them on the spot for incompetence ? -- john r pierce, recycling bits in santa cruz
В списке pgsql-general по дате отправления