[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-sql
Subject:    Re: [SQL] Enhancement to SQL query capabilities
From:       Andrew Smith <laconical () gmail ! com>
Date:       2016-03-18 22:09:43
Message-ID: CALr=acH5M5FgMj4wn3ocBVg=UKtcn4Jw3BfXOX6R6ZbNgWdj5g () mail ! gmail ! com
[Download RAW message or body]

>
> 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's long term interests, in addition to the short term pain/cost…and
> I do feel your pain – there will be no shortcut to the endzone for you,
> with  that much non-standard code to update.



> Aside from the other solutions that have been mentioned, have you
> considered querying a view that contains the desired join?
>
> There's no substitute for fixing that nonstandard syntax, in any case.
> Even if you could persuade pgsql-hackers that the concept was good
> (which I really doubt), they'd not go for using : as a selector.
>
> Thanks for the suggestions guys - using Natural joins and views is
definitely something I'll look into to make selecting data from the
database easier for users/app developers. In terms of insert/update/delete
scripts, I guess I could write something to parse the existing scripts and
update them to ANSI SQL instead of our custom version. That is probably a
better approach than a custom psql that someone else will have to maintain
going forward.

Cheers

Andrew

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span \
style="font-family:Calibri,sans-serif;font-size:14.6667px">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's long term interests, in addition to the short term \
pain/cost…and I do feel your pain – there will be no shortcut to the endzone for \
you, with   that much non-standard code to update.</span></blockquote><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Aside \
from the other solutions that have been mentioned, have you<br> considered querying a \
view that contains the desired join?<br> <br>
There&#39;s no substitute for fixing that nonstandard syntax, in any case.<br>
Even if you could persuade pgsql-hackers that the concept was good<br>
(which I really doubt), they&#39;d not go for using : as a \
selector.<br><br></blockquote><div>Thanks for the suggestions guys - using Natural \
joins and views is definitely something I&#39;ll look into to make selecting data \
from the database easier for users/app developers. In terms of insert/update/delete \
scripts, I guess I could write something to parse the existing scripts and update \
them to ANSI SQL instead of our custom version. That is probably a better approach \
than a custom psql that someone else will have to maintain going forward.  \
</div></div><br></div><div class="gmail_extra">Cheers</div><div \
class="gmail_extra"><br></div><div class="gmail_extra">Andrew</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]