Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1agtQK-0005UH-7b for pgsql-sql@arkaria.postgresql.org; Fri, 18 Mar 2016 12:22:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1agtQJ-0004OE-Qg for pgsql-sql@arkaria.postgresql.org; Fri, 18 Mar 2016 12:22:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1agtQH-0004MW-M7 for pgsql-sql@postgresql.org; Fri, 18 Mar 2016 12:22:33 +0000 Received: from aibo.runbox.com ([91.220.196.211]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1agtQE-00016b-Q7 for pgsql-sql@postgresql.org; Fri, 18 Mar 2016 12:22:33 +0000 Received: from [10.9.9.212] (helo=mailfront12.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1agtQC-0005S8-Az; Fri, 18 Mar 2016 13:22:28 +0100 Received: from cpe-76-176-177-1.san.res.rr.com ([76.176.177.1] helo=seasyslap4) by mailfront12.runbox.com with esmtpsa (uid:561468 ) (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.82) id 1agtPq-0007yY-7f; Fri, 18 Mar 2016 13:22:06 +0100 From: "Mike Sofen" To: "'Andrew Smith'" , "'David G. Johnston'" Cc: References: In-Reply-To: Subject: Re: Enhancement to SQL query capabilities Date: Fri, 18 Mar 2016 05:21:51 -0700 Message-ID: <000a01d18110$c1e6c000$45b44000$@runbox.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01D180D6.1587E800" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQLXJT7f/kCK5NBslS02tyb6WSyQSQGWwgO+AX0EZbsB1SR8D50sjRmQ Content-Language: en-us X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org This is a multipart message in MIME format. ------=_NextPart_000_000B_01D180D6.1587E800 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Andrew, while I get that you want to reduce the scope of re-work on your = project, think about it this way: you=E2=80=99re attempting to convert = code that was never standards compliant with yet another solution that = isn=E2=80=99t standards compliant, and so will have to be converted = again at some point. =20 ANSI SQL exists to allow developers of all types to use a common syntax = across a massive programming landscape. While each database platform = has its own SQL nuances, the core ANSI compliance allows me to code for = Postgres, SQL Server and Mysql with almost no brainwave = activity=E2=80=A6that is so valuable, well, it=E2=80=99s priceless. =20 =20 If you go the route of homebrewing a code solution, the app will stay = outside the coding mainstream, making the next person to take your role = very hard to find, if they can be found at all. I always think of the = customer=E2=80=99s long term interests, in addition to the short term = pain/cost=E2=80=A6and I do feel your pain =E2=80=93 there will be no = shortcut to the endzone for you, with that much non-standard code to = update. =20 Mike =20 From: Andrew Smith Sent: Friday, March 18, 2016 12:00 AM I would have thought that being able to reduce the complexity of long = SQL statements would be seen as a new capability, but if it isn't = desirable then I'll download the code and start looking into it. At the = very least I'll probably have to provide a homebrew alternative to psql = as we've got heaps of scripts written in this syntax which will take a = very long time to port across to standard SQL. ------=_NextPart_000_000B_01D180D6.1587E800 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Andrew, = while I get that you want to reduce the scope of re-work on your = project, think about it this way:=C2=A0 you=E2=80=99re attempting to = convert code that was never standards compliant with yet another = solution that isn=E2=80=99t standards compliant, and so will have to be = converted again at some point.

 

ANSI SQL = exists to allow developers of all types to use a common syntax across a = massive programming landscape.=C2=A0 While each database platform has = its own SQL nuances, the core ANSI compliance allows me to code for = Postgres, SQL Server and Mysql with almost no brainwave = activity=E2=80=A6that is so valuable, well, it=E2=80=99s = priceless.=C2=A0

 

If you go = the route of homebrewing a code solution, the app will stay outside the = coding mainstream, making the next person to take your role very hard to = find, if they can be found at all.=C2=A0 I always think of the = customer=E2=80=99s long term interests, in addition to the short term = pain/cost=E2=80=A6and I do feel your pain =E2=80=93 there will be no = shortcut to the endzone for you, with =C2=A0that much non-standard code = to update.

 

Mike

 

From:<= /b> = Andrew Smith
Sent: Friday, March 18, 2016 12:00 = AM

I would = have thought that being able to reduce the complexity of long SQL = statements would be seen as a new capability, but if it isn't desirable = then I'll download the code and start looking into it. At the very least = I'll probably have to provide a homebrew alternative to psql as we've = got heaps of scripts written in this syntax which will take a very long = time to port across to standard = SQL.

------=_NextPart_000_000B_01D180D6.1587E800--