Re: Format

On 09/29/2015 06:13 AM, Ramesh T wrote:
>
>
> On Tue, Sep 29, 2015 at 6:43 PM, Ramesh T <rameshparnanditech@gmail.com
> <mailto:rameshparnanditech@gmail.com>> wrote:
>
>     in my mind to be beautiful ,avoid confusion to understand sql query code
>
>     like
>
>     select abcd,cde,rfg,count(*),bcd,cde,rfg,count(*),bcd,cde,rfg,count(*) ;
>
>     if some one written, then newer or code reader understand easily
>     select abcd,
>                cde,
>                rfg,
>                count(*),
>     ...,
>     ..,
>     ...,
>     like line by line
>
>     in postgres direct option format is not available.i want see code
>     intended proper.
>     in context editor i didn't find format option only like  lower to
>     upper..
>


http://sqlformat.darold.net/

To install locally:
https://github.com/darold/pgFormatter

http://format-sql.de/

To install locally:
https://github.com/paetzke/format-sql

>
>
>     On Mon, Sep 28, 2015 at 11:20 PM, David G. Johnston
>     <david.g.johnston@gmail.com <mailto:david.g.johnston@gmail.com>> wrote:
>
>         CREATE FUNCTION
>         CREATE VIEW
>
>         As yes, I am being mostly serious - though I have been pondering
>         seeing what tools can do as opposed to the manual formatting
>         I've been performing.  Even a basic linter would be helpful...
>
>         The big problem is you need to define what it means to be
>         beautiful.  Understandable is a totally different area and that
>         is more where views and functions come in so you can provide
>         names to the various constructs you are using.  CTE/WITH
>         facilitate this as well.
>
>         David J.
>
>
>         On Mon, Sep 28, 2015 at 8:45 AM, Ramesh T
>         <rameshparnanditech@gmail.com
>         <mailto:rameshparnanditech@gmail.com>> wrote:
>
>             Hi All,
>                        How to change sql format to look beautiful and
>             understandable using pgadmin3 or else ther tools for postgres.
>
>             any help appreciated..
>
>
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com