sql query

sql query

[Jude DaShiell]

I wrote a query in sql using psql for an interactive environment in 
console mode.  I can get a couple different kinds of output neither of 
which would be useful for production level work.  The column names from 
which data was taken in a table would be informative if those were to show 
up to the left of the values but that's a different kind of output and 
what is also happening when I use an aggregate function say 
round(avg(sug),1) is that the function shows with its result on output.  
That particular formula was used to calculate average blood sugar for a 
set of data.  I can use \t and turn off all tuples and then all I read are 
the rounded averages again with no explanatory text.
I understand all of this since I wrote the query but someone else who 
doesn't know what Linux is never mind what postgresql is needing to look 
at this data without assistance is going to have a hard road to travel.
I was reading up on comment (7) but unless those \D directives can operate 
like \t and show column names and comments written for aggregate functions 
that won't be a workable solution.



jude <jdashiel@shellworld.net>

Re: sql query

[Tim Chase]

I'm not quite sure I fully understand the trouble you're having, but
I'm game to take a stab at it, even if it's a SQL/PostgreSQL
question on a Linux list. (grins)  If I understand correctly, you want
to be able to

1) give meaningful names to columns that would otherwise have their
names defaulted (such as from aggregate functions), and

2) make it easier to read by including the headers with each value

You can rename columns using the "AS" keyword if that would help:

  select
   grouping_field,
   round(avg(sug),1) as Rounded_Average,
   count(*) as Count_of_Records
  from some_table
  group by 

That can be combined with the "\x" command to get the headers on each
row with a record-separator.  This should produce output something
like

-[ RECORD 1 ]-
grouping_field | alpha
Rounded_Average | 3.1
Count_of_Records | 3
-[ RECORD 2 ]-
grouping_field | delta
Rounded_Average | 6.2
Count_of_Records | 4
-[ RECORD 3 ]-
grouping_field | gamma
Rounded_Average | 2.5
Count_of_Records | 1


If that doesn't get you what you want, if you can try and describe
more clearly what you want, I can take another stab.  Hope this helps,

-Tim




On May  5, 2014, Jude DaShiell wrote:
> I wrote a query in sql using psql for an interactive environment in 
> console mode.  I can get a couple different kinds of output neither
> of which would be useful for production level work.  The column
> names from which data was taken in a table would be informative if
> those were to show up to the left of the values but that's a
> different kind of output and what is also happening when I use an
> aggregate function say round(avg(sug),1) is that the function shows
> with its result on output. That particular formula was used to
> calculate average blood sugar for a set of data.  I can use \t and
> turn off all tuples and then all I read are the rounded averages
> again with no explanatory text. I understand all of this since I
> wrote the query but someone else who doesn't know what Linux is
> never mind what postgresql is needing to look at this data without
> assistance is going to have a hard road to travel. I was reading up
> on comment (7) but unless those \D directives can operate like \t
> and show column names and comments written for aggregate functions
> that won't be a workable solution.
> 
> 
> 
> jude <jdashiel@shellworld.net>
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

Re: sql query

[Jude DaShiell]

Hi Tim,

I'm pretty sure this will work correctly.  Thanks much; I intend to use 
sql for more tables and data than this one so this help you provided 
will get me well set up for the future.

On Mon, 5 May 2014, Tim Chase wrote:

> I'm not quite sure I fully understand the trouble you're having, but
> I'm game to take a stab at it, even if it's a SQL/PostgreSQL
> question on a Linux list. (grins)  If I understand correctly, you want
> to be able to
> 
> 1) give meaningful names to columns that would otherwise have their
> names defaulted (such as from aggregate functions), and
> 
> 2) make it easier to read by including the headers with each value
> 
> You can rename columns using the "AS" keyword if that would help:
> 
>   select
>    grouping_field,
>    round(avg(sug),1) as Rounded_Average,
>    count(*) as Count_of_Records
>   from some_table
>   group by 
> 
> That can be combined with the "\x" command to get the headers on each
> row with a record-separator.  This should produce output something
> like
> 
> -[ RECORD 1 ]-
> grouping_field | alpha
> Rounded_Average | 3.1
> Count_of_Records | 3
> -[ RECORD 2 ]-
> grouping_field | delta
> Rounded_Average | 6.2
> Count_of_Records | 4
> -[ RECORD 3 ]-
> grouping_field | gamma
> Rounded_Average | 2.5
> Count_of_Records | 1
> 
> 
> If that doesn't get you what you want, if you can try and describe
> more clearly what you want, I can take another stab.  Hope this helps,
> 
> -Tim
> 
> 
> 
> 
> On May  5, 2014, Jude DaShiell wrote:
> > I wrote a query in sql using psql for an interactive environment in 
> > console mode.  I can get a couple different kinds of output neither
> > of which would be useful for production level work.  The column
> > names from which data was taken in a table would be informative if
> > those were to show up to the left of the values but that's a
> > different kind of output and what is also happening when I use an
> > aggregate function say round(avg(sug),1) is that the function shows
> > with its result on output. That particular formula was used to
> > calculate average blood sugar for a set of data.  I can use \t and
> > turn off all tuples and then all I read are the rounded averages
> > again with no explanatory text. I understand all of this since I
> > wrote the query but someone else who doesn't know what Linux is
> > never mind what postgresql is needing to look at this data without
> > assistance is going to have a hard road to travel. I was reading up
> > on comment (7) but unless those \D directives can operate like \t
> > and show column names and comments written for aggregate functions
> > that won't be a workable solution.
> > 
> > 
> > 
> > jude <jdashiel@shellworld.net>
> > 
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
> 
> 

jude <jdashiel@shellworld.net>

Re: sql query

[Jude DaShiell]

Now, everything is working correctly if anyone else ever needs this it's 
available.
cut here.
select
min(date) as "starting date:",
max(date) as "ending date:",
count(cys) as "Cystalic sample size:",
 round(avg(cys),1) as "Average Cystalic Pressure:",
min(cys) as "Min Cystalic Pressure:",
max(cys) as "Max cystalic Pressure:",
 (select cys
  from health
  group by cys
  order by count(cys) desc, cys
  limit 1) as "Mode Cystalic Pressure:",
count(dya) as "dyastalic sample size:",
round(avg(dya),1) as "Average Dyastalic Pressure:",
min(dya) as "Min Dyastalic Pressure:",
Max(dya) as "Max Dyastalic Pressure:",
 (select dya
  from health
  group by dya
  order by count(dya) desc, dya
  limit 1) as "Mode Dyastalic Pressure:",
count(pul) as "Pulse Sample Size:",
round(avg(pul),1) as "Average Pulse:",
min(pul) as "Min Pulse:",
max(pul) as "Max Pulse:",
 (select pul
  from health
  group by pul
  order by count(pul) desc, pul
  limit 1) as "Mode Pulse:",
count(sug) as "Sugar Sample Size:",
 round(avg(sug),1) as "Average Sugar:",
min(sug) as "Min Sugar:",
max(sug) as "Max Sugar:",
 (select sug
  from health
  group by sug
  order by count(sug) desc, sug
  limit 1) as "Mode Sugar:"
from health;

cut here.
I studied Mastering Oracle SQL as requested by my employer then the 
skill I had picked up was never later put to use and got rusty.  Thanks 
forhelp with the rust Tim.

On Mon, 5 May 2014, Tim Chase wrote:

> I'm not quite sure I fully understand the trouble you're having, but
> I'm game to take a stab at it, even if it's a SQL/PostgreSQL
> question on a Linux list. (grins)  If I understand correctly, you want
> to be able to
> 
> 1) give meaningful names to columns that would otherwise have their
> names defaulted (such as from aggregate functions), and
> 
> 2) make it easier to read by including the headers with each value
> 
> You can rename columns using the "AS" keyword if that would help:
> 
>   select
>    grouping_field,
>    round(avg(sug),1) as Rounded_Average,
>    count(*) as Count_of_Records
>   from some_table
>   group by 
> 
> That can be combined with the "\x" command to get the headers on each
> row with a record-separator.  This should produce output something
> like
> 
> -[ RECORD 1 ]-
> grouping_field | alpha
> Rounded_Average | 3.1
> Count_of_Records | 3
> -[ RECORD 2 ]-
> grouping_field | delta
> Rounded_Average | 6.2
> Count_of_Records | 4
> -[ RECORD 3 ]-
> grouping_field | gamma
> Rounded_Average | 2.5
> Count_of_Records | 1
> 
> 
> If that doesn't get you what you want, if you can try and describe
> more clearly what you want, I can take another stab.  Hope this helps,
> 
> -Tim
> 
> 
> 
> 
> On May  5, 2014, Jude DaShiell wrote:
> > I wrote a query in sql using psql for an interactive environment in 
> > console mode.  I can get a couple different kinds of output neither
> > of which would be useful for production level work.  The column
> > names from which data was taken in a table would be informative if
> > those were to show up to the left of the values but that's a
> > different kind of output and what is also happening when I use an
> > aggregate function say round(avg(sug),1) is that the function shows
> > with its result on output. That particular formula was used to
> > calculate average blood sugar for a set of data.  I can use \t and
> > turn off all tuples and then all I read are the rounded averages
> > again with no explanatory text. I understand all of this since I
> > wrote the query but someone else who doesn't know what Linux is
> > never mind what postgresql is needing to look at this data without
> > assistance is going to have a hard road to travel. I was reading up
> > on comment (7) but unless those \D directives can operate like \t
> > and show column names and comments written for aggregate functions
> > that won't be a workable solution.
> > 
> > 
> > 
> > jude <jdashiel@shellworld.net>
> > 
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
> 
> 

jude <jdashiel@shellworld.net>

Re: sql query

[Rob Harris]

Well done!...   so many years since I did anything like this, so duly 
impressed and fascinated.

RobH.
----- Original Message ----- 
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: "Linux for blind general discussion" <blinux-list@redhat.com>
Sent: Wednesday, May 07, 2014 9:01 PM
Subject: Re: sql query


Now, everything is working correctly if anyone else ever needs this it's
available.
cut here.
select
min(date) as "starting date:",
max(date) as "ending date:",
count(cys) as "Cystalic sample size:",
 round(avg(cys),1) as "Average Cystalic Pressure:",
min(cys) as "Min Cystalic Pressure:",
max(cys) as "Max cystalic Pressure:",
 (select cys
  from health
  group by cys
  order by count(cys) desc, cys
  limit 1) as "Mode Cystalic Pressure:",
count(dya) as "dyastalic sample size:",
round(avg(dya),1) as "Average Dyastalic Pressure:",
min(dya) as "Min Dyastalic Pressure:",
Max(dya) as "Max Dyastalic Pressure:",
 (select dya
  from health
  group by dya
  order by count(dya) desc, dya
  limit 1) as "Mode Dyastalic Pressure:",
count(pul) as "Pulse Sample Size:",
round(avg(pul),1) as "Average Pulse:",
min(pul) as "Min Pulse:",
max(pul) as "Max Pulse:",
 (select pul
  from health
  group by pul
  order by count(pul) desc, pul
  limit 1) as "Mode Pulse:",
count(sug) as "Sugar Sample Size:",
 round(avg(sug),1) as "Average Sugar:",
min(sug) as "Min Sugar:",
max(sug) as "Max Sugar:",
 (select sug
  from health
  group by sug
  order by count(sug) desc, sug
  limit 1) as "Mode Sugar:"
from health;

cut here.
I studied Mastering Oracle SQL as requested by my employer then the
skill I had picked up was never later put to use and got rusty.  Thanks
forhelp with the rust Tim.

On Mon, 5 May 2014, Tim Chase wrote:

> I'm not quite sure I fully understand the trouble you're having, but
> I'm game to take a stab at it, even if it's a SQL/PostgreSQL
> question on a Linux list. (grins)  If I understand correctly, you want
> to be able to
>
> 1) give meaningful names to columns that would otherwise have their
> names defaulted (such as from aggregate functions), and
>
> 2) make it easier to read by including the headers with each value
>
> You can rename columns using the "AS" keyword if that would help:
>
>   select
>    grouping_field,
>    round(avg(sug),1) as Rounded_Average,
>    count(*) as Count_of_Records
>   from some_table
>   group by
>
> That can be combined with the "\x" command to get the headers on each
> row with a record-separator.  This should produce output something
> like
>
> -[ RECORD 1 ]-
> grouping_field | alpha
> Rounded_Average | 3.1
> Count_of_Records | 3
> -[ RECORD 2 ]-
> grouping_field | delta
> Rounded_Average | 6.2
> Count_of_Records | 4
> -[ RECORD 3 ]-
> grouping_field | gamma
> Rounded_Average | 2.5
> Count_of_Records | 1
>
>
> If that doesn't get you what you want, if you can try and describe
> more clearly what you want, I can take another stab.  Hope this helps,
>
> -Tim
>
>
>
>
> On May  5, 2014, Jude DaShiell wrote:
> > I wrote a query in sql using psql for an interactive environment in
> > console mode.  I can get a couple different kinds of output neither
> > of which would be useful for production level work.  The column
> > names from which data was taken in a table would be informative if
> > those were to show up to the left of the values but that's a
> > different kind of output and what is also happening when I use an
> > aggregate function say round(avg(sug),1) is that the function shows
> > with its result on output. That particular formula was used to
> > calculate average blood sugar for a set of data.  I can use \t and
> > turn off all tuples and then all I read are the rounded averages
> > again with no explanatory text. I understand all of this since I
> > wrote the query but someone else who doesn't know what Linux is
> > never mind what postgresql is needing to look at this data without
> > assistance is going to have a hard road to travel. I was reading up
> > on comment (7) but unless those \D directives can operate like \t
> > and show column names and comments written for aggregate functions
> > that won't be a workable solution.
> >
> >
> >
> > jude <jdashiel@shellworld.net>
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>

jude <jdashiel@shellworld.net>

_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list 

Re: sql query

[Jude DaShiell]

I'll be commenting that sql file and adding Tim Chase to the credits 
too.  Tim I hope I didn't murder your last name.

On Thu, 8 May 2014, Rob Harris wrote:

> Well done!...   so many years since I did anything like this, so duly 
> impressed and fascinated.
> 
> RobH.
> ----- Original Message ----- 
> From: "Jude DaShiell" <jdashiel@shellworld.net>
> To: "Linux for blind general discussion" <blinux-list@redhat.com>
> Sent: Wednesday, May 07, 2014 9:01 PM
> Subject: Re: sql query
> 
> 
> Now, everything is working correctly if anyone else ever needs this it's
> available.
> cut here.
> select
> min(date) as "starting date:",
> max(date) as "ending date:",
> count(cys) as "Cystalic sample size:",
>  round(avg(cys),1) as "Average Cystalic Pressure:",
> min(cys) as "Min Cystalic Pressure:",
> max(cys) as "Max cystalic Pressure:",
>  (select cys
>   from health
>   group by cys
>   order by count(cys) desc, cys
>   limit 1) as "Mode Cystalic Pressure:",
> count(dya) as "dyastalic sample size:",
> round(avg(dya),1) as "Average Dyastalic Pressure:",
> min(dya) as "Min Dyastalic Pressure:",
> Max(dya) as "Max Dyastalic Pressure:",
>  (select dya
>   from health
>   group by dya
>   order by count(dya) desc, dya
>   limit 1) as "Mode Dyastalic Pressure:",
> count(pul) as "Pulse Sample Size:",
> round(avg(pul),1) as "Average Pulse:",
> min(pul) as "Min Pulse:",
> max(pul) as "Max Pulse:",
>  (select pul
>   from health
>   group by pul
>   order by count(pul) desc, pul
>   limit 1) as "Mode Pulse:",
> count(sug) as "Sugar Sample Size:",
>  round(avg(sug),1) as "Average Sugar:",
> min(sug) as "Min Sugar:",
> max(sug) as "Max Sugar:",
>  (select sug
>   from health
>   group by sug
>   order by count(sug) desc, sug
>   limit 1) as "Mode Sugar:"
> from health;
> 
> cut here.
> I studied Mastering Oracle SQL as requested by my employer then the
> skill I had picked up was never later put to use and got rusty.  Thanks
> forhelp with the rust Tim.
> 
> On Mon, 5 May 2014, Tim Chase wrote:
> 
> > I'm not quite sure I fully understand the trouble you're having, but
> > I'm game to take a stab at it, even if it's a SQL/PostgreSQL
> > question on a Linux list. (grins)  If I understand correctly, you want
> > to be able to
> >
> > 1) give meaningful names to columns that would otherwise have their
> > names defaulted (such as from aggregate functions), and
> >
> > 2) make it easier to read by including the headers with each value
> >
> > You can rename columns using the "AS" keyword if that would help:
> >
> >   select
> >    grouping_field,
> >    round(avg(sug),1) as Rounded_Average,
> >    count(*) as Count_of_Records
> >   from some_table
> >   group by
> >
> > That can be combined with the "\x" command to get the headers on each
> > row with a record-separator.  This should produce output something
> > like
> >
> > -[ RECORD 1 ]-
> > grouping_field | alpha
> > Rounded_Average | 3.1
> > Count_of_Records | 3
> > -[ RECORD 2 ]-
> > grouping_field | delta
> > Rounded_Average | 6.2
> > Count_of_Records | 4
> > -[ RECORD 3 ]-
> > grouping_field | gamma
> > Rounded_Average | 2.5
> > Count_of_Records | 1
> >
> >
> > If that doesn't get you what you want, if you can try and describe
> > more clearly what you want, I can take another stab.  Hope this helps,
> >
> > -Tim
> >
> >
> >
> >
> > On May  5, 2014, Jude DaShiell wrote:
> > > I wrote a query in sql using psql for an interactive environment in
> > > console mode.  I can get a couple different kinds of output neither
> > > of which would be useful for production level work.  The column
> > > names from which data was taken in a table would be informative if
> > > those were to show up to the left of the values but that's a
> > > different kind of output and what is also happening when I use an
> > > aggregate function say round(avg(sug),1) is that the function shows
> > > with its result on output. That particular formula was used to
> > > calculate average blood sugar for a set of data.  I can use \t and
> > > turn off all tuples and then all I read are the rounded averages
> > > again with no explanatory text. I understand all of this since I
> > > wrote the query but someone else who doesn't know what Linux is
> > > never mind what postgresql is needing to look at this data without
> > > assistance is going to have a hard road to travel. I was reading up
> > > on comment (7) but unless those \D directives can operate like \t
> > > and show column names and comments written for aggregate functions
> > > that won't be a workable solution.
> > >
> > >
> > >
> > > jude <jdashiel@shellworld.net>
> > >
> > > _______________________________________________
> > > Blinux-list mailing list
> > > Blinux-list@redhat.com
> > > https://www.redhat.com/mailman/listinfo/blinux-list
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> >
> >
> 
> jude <jdashiel@shellworld.net>
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
> 
> 

jude <jdashiel@shellworld.net>

Re: sql query

[Jude DaShiell]

What do you make of this?

Script started on Sat 25 Oct 2014 06:20:46 PM EDT
The Moon is Waxing Crescent (4% of Full)
Time: 06:20:46 PM 
 Date: Saturday October 25 2014 
 Week: 42 
 Day Of Year: 298
[jude@athame ~]$ psql -x
psql (9.3.5)
Type "help" for help.

jude=# \i phealth1.sql
psql:phealth1.sql:97: ERROR:  missing FROM-clause entry for table "h"
LINE 66:  (select h.dyastalic_pressure
                  ^
jude=# \q
[jude@athame ~]$ exit
exit

Script done on Sat 25 Oct 2014 06:21:51 PM EDT

jude <jdashiel@shellworld.net>
Twitter: @jdashiel

Re: sql query

[Rob Harris]

Interesting, if pedantic response;  good job iPhone don't jabber on with all 
that.

Rh.
----- Original Message ----- 
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: "Linux for blind general discussion" <blinux-list@redhat.com>
Sent: Saturday, October 25, 2014 10:30 PM
Subject: Re: sql query


What do you make of this?

Script started on Sat 25 Oct 2014 06:20:46 PM EDT
The Moon is Waxing Crescent (4% of Full)
Time: 06:20:46 PM
 Date: Saturday October 25 2014
 Week: 42
 Day Of Year: 298
[jude@athame ~]$ psql -x
psql (9.3.5)
Type "help" for help.

jude=# \i phealth1.sql
psql:phealth1.sql:97: ERROR:  missing FROM-clause entry for table "h"
LINE 66:  (select h.dyastalic_pressure
                  ^
jude=# \q
[jude@athame ~]$ exit
exit

Script done on Sat 25 Oct 2014 06:21:51 PM EDT

jude <jdashiel@shellworld.net>
Twitter: @jdashiel

_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list 

Re: sql query

[Tim Chase]

On October 25, 2014, Jude DaShiell wrote:
> jude=# \i phealth1.sql
> psql:phealth1.sql:97: ERROR:  missing FROM-clause entry for table
> "h" LINE 66:  (select h.dyastalic_pressure

Ah, my apologies.  Without actual database access, it's a bit tough
to vet these queries.  I was missing some table aliases that I've put
in the SQL below.  Sorry 'bout that.

-tim


select
 'Combined' as Title,
 min(date) as "Starting Date:",
 max(date) as "Ending Date:",
 count(cystalic_pressure) as "Cystalic Sample Size:",
 round(avg(cystalic_pressure),1) as "Average Cystalic Pressure:",
 min(cystalic_pressure) as "Min Cystalic Pressure:",
 max(cystalic_pressure) as "Max Cystalic Pressure:",
 (select h.cystalic_pressure
  from health h
  where date between now() - interval '1 week' and now()
  group by h.cystalic_pressure
  order by count(h.cystalic_pressure) desc, h.cystalic_pressure
  limit 1) as "Mode Cystalic Pressure:",
 count(dyastalic_pressure) as "Dyastalic Sample Size:",
 round(avg(dyastalic_pressure),1) as "Average Dyastalic Pressure:",
 min(dyastalic_pressure) as "Min Dyastalic Pressure:",
 max(dyastalic_pressure) as "Max Dyastalic Pressure:",
 (select h.dyastalic_pressure
  from health h
  where date between now() - interval '1 week' and now()
  group by h.dyastalic_pressure
  order by count(h.dyastalic_pressure) desc, h.dyastalic_pressure
  limit 1) as "Mode Dyastalic Pressure:",
 count(pulse) as "Pulse Sample Size:",
 round(avg(pulse),1) as "Average Pulse:",
 min(pulse) as "Min Pulse:",
 max(pulse) as "Max Pulse:",
 (select h.pulse
  from health h
  where date between now() - interval '1 week' and now()
  group by h.pulse
  order by count(h.pulse) desc, h.pulse
  limit 1) as "Mode Pulse:",
 count(blood_sugar) as "Sugar Sample Size:",
 round(avg(blood_sugar),1) as "Average Sugar:",
 min(blood_sugar) as "Min Sugar:",
 max(blood_sugar) as "Max Sugar:",
 (select h.blood_sugar
  from health h
  where date between now() - interval '1 week' and now()
  group by h.blood_sugar
  order by count(h.blood_sugar) desc, h.blood_sugar
  limit 1) as "Mode Sugar:"
from health
where date between now() - interval '1 week' and now()

union all

select
 to_char(date, 'Day') as Title,
 date as "Starting Date:",
 date as "Ending Date:",
 count(cystalic_pressure) as "Cystalic Sample Size:",
 round(avg(cystalic_pressure),1) as "Average Cystalic Pressure:",
 min(cystalic_pressure) as "Min Cystalic Pressure:",
 max(cystalic_pressure) as "Max Cystalic Pressure:",
 (select h.cystalic_pressure
  from health h
  where h.date = health.date
  group by h.cystalic_pressure
  order by count(h.cystalic_pressure) desc, h.cystalic_pressure
  limit 1) as "Mode Cystalic Pressure:",
 count(dyastalic_pressure) as "Dyastalic Sample Size:",
 round(avg(dyastalic_pressure),1) as "Average Dyastalic Pressure:",
 min(dyastalic_pressure) as "Min Dyastalic Pressure:",
 max(dyastalic_pressure) as "Max Dyastalic Pressure:",
 (select h.dyastalic_pressure
  from health h
  where h.date = health.date
  group by h.dyastalic_pressure
  order by count(h.dyastalic_pressure) desc, h.dyastalic_pressure
  limit 1) as "Mode Dyastalic Pressure:",
 count(pulse) as "Pulse Sample Size:",
 round(avg(pulse),1) as "Average Pulse:",
 min(pulse) as "Min Pulse:",
 max(pulse) as "Max Pulse:",
 (select h.pulse
  from health h
  where h.date = health.date
  group by h.pulse
  order by count(h.pulse) desc, h.pulse
  limit 1) as "Mode Pulse:",
 count(blood_sugar) as "Sugar Sample Size:",
 round(avg(blood_sugar),1) as "Average Sugar:",
 min(blood_sugar) as "Min Sugar:",
 max(blood_sugar) as "Max Sugar:",
 (select h.blood_sugar
  from health h
  where h.date = health.date
  group by h.blood_sugar
  order by count(h.blood_sugar) desc, h.blood_sugar
  limit 1) as "Mode Sugar:"
from health
where date >= now() - interval '1 week'
group by date
order by "Starting Date:", Title;

Re: sql query

[Jude DaShiell]

Hi Tim,

This may help:
create table health ( 
date   date PRIMARY KEY,
Cystalic_Pressure    int NOT NULL, check (Cystalic_Pressure > 0),
--- cystalic pressure
Dyastalic_Pressure int NOT NULL, check (Dyastalic_Pressure > 0),
--- dyastalic pressure
Pulse int NOT NULL, check (Pulse > 0),
--- pulse
Blood_Sugar int NOT NULL, check (Blood_Sugar > 0),
--- blood sugar
weekday int NOT NULL, check (weekday > -1), check (weekday < 7)
--- weekday number saturday=6
);
On Sun, 26 Oct 2014, Tim Chase wrote:

> On October 25, 2014, Jude DaShiell wrote:
> > jude=# \i phealth1.sql
> > psql:phealth1.sql:97: ERROR:  missing FROM-clause entry for table
> > "h" LINE 66:  (select h.dyastalic_pressure
> 
> Ah, my apologies.  Without actual database access, it's a bit tough
> to vet these queries.  I was missing some table aliases that I've put
> in the SQL below.  Sorry 'bout that.
> 
> -tim
> 
> 
> select
>  'Combined' as Title,
>  min(date) as "Starting Date:",
>  max(date) as "Ending Date:",
>  count(cystalic_pressure) as "Cystalic Sample Size:",
>  round(avg(cystalic_pressure),1) as "Average Cystalic Pressure:",
>  min(cystalic_pressure) as "Min Cystalic Pressure:",
>  max(cystalic_pressure) as "Max Cystalic Pressure:",
>  (select h.cystalic_pressure
>   from health h
>   where date between now() - interval '1 week' and now()
>   group by h.cystalic_pressure
>   order by count(h.cystalic_pressure) desc, h.cystalic_pressure
>   limit 1) as "Mode Cystalic Pressure:",
>  count(dyastalic_pressure) as "Dyastalic Sample Size:",
>  round(avg(dyastalic_pressure),1) as "Average Dyastalic Pressure:",
>  min(dyastalic_pressure) as "Min Dyastalic Pressure:",
>  max(dyastalic_pressure) as "Max Dyastalic Pressure:",
>  (select h.dyastalic_pressure
>   from health h
>   where date between now() - interval '1 week' and now()
>   group by h.dyastalic_pressure
>   order by count(h.dyastalic_pressure) desc, h.dyastalic_pressure
>   limit 1) as "Mode Dyastalic Pressure:",
>  count(pulse) as "Pulse Sample Size:",
>  round(avg(pulse),1) as "Average Pulse:",
>  min(pulse) as "Min Pulse:",
>  max(pulse) as "Max Pulse:",
>  (select h.pulse
>   from health h
>   where date between now() - interval '1 week' and now()
>   group by h.pulse
>   order by count(h.pulse) desc, h.pulse
>   limit 1) as "Mode Pulse:",
>  count(blood_sugar) as "Sugar Sample Size:",
>  round(avg(blood_sugar),1) as "Average Sugar:",
>  min(blood_sugar) as "Min Sugar:",
>  max(blood_sugar) as "Max Sugar:",
>  (select h.blood_sugar
>   from health h
>   where date between now() - interval '1 week' and now()
>   group by h.blood_sugar
>   order by count(h.blood_sugar) desc, h.blood_sugar
>   limit 1) as "Mode Sugar:"
> from health
> where date between now() - interval '1 week' and now()
> 
> union all
> 
> select
>  to_char(date, 'Day') as Title,
>  date as "Starting Date:",
>  date as "Ending Date:",
>  count(cystalic_pressure) as "Cystalic Sample Size:",
>  round(avg(cystalic_pressure),1) as "Average Cystalic Pressure:",
>  min(cystalic_pressure) as "Min Cystalic Pressure:",
>  max(cystalic_pressure) as "Max Cystalic Pressure:",
>  (select h.cystalic_pressure
>   from health h
>   where h.date = health.date
>   group by h.cystalic_pressure
>   order by count(h.cystalic_pressure) desc, h.cystalic_pressure
>   limit 1) as "Mode Cystalic Pressure:",
>  count(dyastalic_pressure) as "Dyastalic Sample Size:",
>  round(avg(dyastalic_pressure),1) as "Average Dyastalic Pressure:",
>  min(dyastalic_pressure) as "Min Dyastalic Pressure:",
>  max(dyastalic_pressure) as "Max Dyastalic Pressure:",
>  (select h.dyastalic_pressure
>   from health h
>   where h.date = health.date
>   group by h.dyastalic_pressure
>   order by count(h.dyastalic_pressure) desc, h.dyastalic_pressure
>   limit 1) as "Mode Dyastalic Pressure:",
>  count(pulse) as "Pulse Sample Size:",
>  round(avg(pulse),1) as "Average Pulse:",
>  min(pulse) as "Min Pulse:",
>  max(pulse) as "Max Pulse:",
>  (select h.pulse
>   from health h
>   where h.date = health.date
>   group by h.pulse
>   order by count(h.pulse) desc, h.pulse
>   limit 1) as "Mode Pulse:",
>  count(blood_sugar) as "Sugar Sample Size:",
>  round(avg(blood_sugar),1) as "Average Sugar:",
>  min(blood_sugar) as "Min Sugar:",
>  max(blood_sugar) as "Max Sugar:",
>  (select h.blood_sugar
>   from health h
>   where h.date = health.date
>   group by h.blood_sugar
>   order by count(h.blood_sugar) desc, h.blood_sugar
>   limit 1) as "Mode Sugar:"
> from health
> where date >= now() - interval '1 week'
> group by date
> order by "Starting Date:", Title;
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
> 
> 

jude <jdashiel@shellworld.net>
Twitter: @jdashiel

Re: sql query

[Tim Chase]

It does help a bit.  It looks like you only take one measurement each
day (the date is a PRIMARY KEY so it has to be unique).  Based on
what I'm seeing of your various queries (particularly where you're
rebuilding the weekday tables), it looks like your aim is to aggregate
across all Monday samples, all Tuesday samples, etc. (not just the
most recent Monday samples).  Is this your intent?  Or do you purge
out data older than a week?

-tim

On October 28, 2014, Jude DaShiell wrote:
> Hi Tim,
> 
> This may help:
> create table health ( 
> date   date PRIMARY KEY,
> Cystalic_Pressure    int NOT NULL, check (Cystalic_Pressure > 0),
> --- cystalic pressure
> Dyastalic_Pressure int NOT NULL, check (Dyastalic_Pressure > 0),
> --- dyastalic pressure
> Pulse int NOT NULL, check (Pulse > 0),
> --- pulse
> Blood_Sugar int NOT NULL, check (Blood_Sugar > 0),
> --- blood sugar
> weekday int NOT NULL, check (weekday > -1), check (weekday < 7)
> --- weekday number saturday=6
> );
> On Sun, 26 Oct 2014, Tim Chase wrote:
> 
> > On October 25, 2014, Jude DaShiell wrote:
> > > jude=# \i phealth1.sql
> > > psql:phealth1.sql:97: ERROR:  missing FROM-clause entry for
> > > table "h" LINE 66:  (select h.dyastalic_pressure
> > 
> > Ah, my apologies.  Without actual database access, it's a bit
> > tough to vet these queries.  I was missing some table aliases
> > that I've put in the SQL below.  Sorry 'bout that.
> > 
> > -tim
> > 
> > 
> > select
> >  'Combined' as Title,
> >  min(date) as "Starting Date:",
> >  max(date) as "Ending Date:",
> >  count(cystalic_pressure) as "Cystalic Sample Size:",
> >  round(avg(cystalic_pressure),1) as "Average Cystalic Pressure:",
> >  min(cystalic_pressure) as "Min Cystalic Pressure:",
> >  max(cystalic_pressure) as "Max Cystalic Pressure:",
> >  (select h.cystalic_pressure
> >   from health h
> >   where date between now() - interval '1 week' and now()
> >   group by h.cystalic_pressure
> >   order by count(h.cystalic_pressure) desc, h.cystalic_pressure
> >   limit 1) as "Mode Cystalic Pressure:",
> >  count(dyastalic_pressure) as "Dyastalic Sample Size:",
> >  round(avg(dyastalic_pressure),1) as "Average Dyastalic
> > Pressure:", min(dyastalic_pressure) as "Min Dyastalic Pressure:",
> >  max(dyastalic_pressure) as "Max Dyastalic Pressure:",
> >  (select h.dyastalic_pressure
> >   from health h
> >   where date between now() - interval '1 week' and now()
> >   group by h.dyastalic_pressure
> >   order by count(h.dyastalic_pressure) desc, h.dyastalic_pressure
> >   limit 1) as "Mode Dyastalic Pressure:",
> >  count(pulse) as "Pulse Sample Size:",
> >  round(avg(pulse),1) as "Average Pulse:",
> >  min(pulse) as "Min Pulse:",
> >  max(pulse) as "Max Pulse:",
> >  (select h.pulse
> >   from health h
> >   where date between now() - interval '1 week' and now()
> >   group by h.pulse
> >   order by count(h.pulse) desc, h.pulse
> >   limit 1) as "Mode Pulse:",
> >  count(blood_sugar) as "Sugar Sample Size:",
> >  round(avg(blood_sugar),1) as "Average Sugar:",
> >  min(blood_sugar) as "Min Sugar:",
> >  max(blood_sugar) as "Max Sugar:",
> >  (select h.blood_sugar
> >   from health h
> >   where date between now() - interval '1 week' and now()
> >   group by h.blood_sugar
> >   order by count(h.blood_sugar) desc, h.blood_sugar
> >   limit 1) as "Mode Sugar:"
> > from health
> > where date between now() - interval '1 week' and now()
> > 
> > union all
> > 
> > select
> >  to_char(date, 'Day') as Title,
> >  date as "Starting Date:",
> >  date as "Ending Date:",
> >  count(cystalic_pressure) as "Cystalic Sample Size:",
> >  round(avg(cystalic_pressure),1) as "Average Cystalic Pressure:",
> >  min(cystalic_pressure) as "Min Cystalic Pressure:",
> >  max(cystalic_pressure) as "Max Cystalic Pressure:",
> >  (select h.cystalic_pressure
> >   from health h
> >   where h.date = health.date
> >   group by h.cystalic_pressure
> >   order by count(h.cystalic_pressure) desc, h.cystalic_pressure
> >   limit 1) as "Mode Cystalic Pressure:",
> >  count(dyastalic_pressure) as "Dyastalic Sample Size:",
> >  round(avg(dyastalic_pressure),1) as "Average Dyastalic
> > Pressure:", min(dyastalic_pressure) as "Min Dyastalic Pressure:",
> >  max(dyastalic_pressure) as "Max Dyastalic Pressure:",
> >  (select h.dyastalic_pressure
> >   from health h
> >   where h.date = health.date
> >   group by h.dyastalic_pressure
> >   order by count(h.dyastalic_pressure) desc, h.dyastalic_pressure
> >   limit 1) as "Mode Dyastalic Pressure:",
> >  count(pulse) as "Pulse Sample Size:",
> >  round(avg(pulse),1) as "Average Pulse:",
> >  min(pulse) as "Min Pulse:",
> >  max(pulse) as "Max Pulse:",
> >  (select h.pulse
> >   from health h
> >   where h.date = health.date
> >   group by h.pulse
> >   order by count(h.pulse) desc, h.pulse
> >   limit 1) as "Mode Pulse:",
> >  count(blood_sugar) as "Sugar Sample Size:",
> >  round(avg(blood_sugar),1) as "Average Sugar:",
> >  min(blood_sugar) as "Min Sugar:",
> >  max(blood_sugar) as "Max Sugar:",
> >  (select h.blood_sugar
> >   from health h
> >   where h.date = health.date
> >   group by h.blood_sugar
> >   order by count(h.blood_sugar) desc, h.blood_sugar
> >   limit 1) as "Mode Sugar:"
> > from health
> > where date >= now() - interval '1 week'
> > group by date
> > order by "Starting Date:", Title;
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> > 
> > 
> 
> jude <jdashiel@shellworld.net>
> Twitter: @jdashiel
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

Re: sql query

[Jude DaShiell]

Yes Tim, that's my intent.  I don't purge data since the menu hasn't yet 
changed here.  I will have to work on the select statements since really 
what should come up is the sample sizes broken by Doctor visit dates.  
The first sample really started April 27, 2014 and ended June 6, 2014 
the second sample ran from June 7, 2014 to August 22, 2014, and this 
third sample runs from August 23, 2014 through some date I think 
February 12, 2015 but I'll check on that over at the office later today. 
 I can reconstruct the health table by feeding it selective record sets 
when I want to find out about these smaller sample sizes as opposed to 
the whole data set.

On Wed, 29 Oct 2014, Tim Chase wrote:

> It does help a bit.  It looks like you only take one measurement each
> day (the date is a PRIMARY KEY so it has to be unique).  Based on
> what I'm seeing of your various queries (particularly where you're
> rebuilding the weekday tables), it looks like your aim is to aggregate
> across all Monday samples, all Tuesday samples, etc. (not just the
> most recent Monday samples).  Is this your intent?  Or do you purge
> out data older than a week?
> 
> -tim
> 
> On October 28, 2014, Jude DaShiell wrote:
> > Hi Tim,
> > 
> > This may help:
> > create table health ( 
> > date   date PRIMARY KEY,
> > Cystalic_Pressure    int NOT NULL, check (Cystalic_Pressure > 0),
> > --- cystalic pressure
> > Dyastalic_Pressure int NOT NULL, check (Dyastalic_Pressure > 0),
> > --- dyastalic pressure
> > Pulse int NOT NULL, check (Pulse > 0),
> > --- pulse
> > Blood_Sugar int NOT NULL, check (Blood_Sugar > 0),
> > --- blood sugar
> > weekday int NOT NULL, check (weekday > -1), check (weekday < 7)
> > --- weekday number saturday=6
> > );
> > On Sun, 26 Oct 2014, Tim Chase wrote:
> > 
> > > On October 25, 2014, Jude DaShiell wrote:
> > > > jude=# \i phealth1.sql
> > > > psql:phealth1.sql:97: ERROR:  missing FROM-clause entry for
> > > > table "h" LINE 66:  (select h.dyastalic_pressure
> > > 
> > > Ah, my apologies.  Without actual database access, it's a bit
> > > tough to vet these queries.  I was missing some table aliases
> > > that I've put in the SQL below.  Sorry 'bout that.
> > > 
> > > -tim
> > > 
> > > 
> > > select
> > >  'Combined' as Title,
> > >  min(date) as "Starting Date:",
> > >  max(date) as "Ending Date:",
> > >  count(cystalic_pressure) as "Cystalic Sample Size:",
> > >  round(avg(cystalic_pressure),1) as "Average Cystalic Pressure:",
> > >  min(cystalic_pressure) as "Min Cystalic Pressure:",
> > >  max(cystalic_pressure) as "Max Cystalic Pressure:",
> > >  (select h.cystalic_pressure
> > >   from health h
> > >   where date between now() - interval '1 week' and now()
> > >   group by h.cystalic_pressure
> > >   order by count(h.cystalic_pressure) desc, h.cystalic_pressure
> > >   limit 1) as "Mode Cystalic Pressure:",
> > >  count(dyastalic_pressure) as "Dyastalic Sample Size:",
> > >  round(avg(dyastalic_pressure),1) as "Average Dyastalic
> > > Pressure:", min(dyastalic_pressure) as "Min Dyastalic Pressure:",
> > >  max(dyastalic_pressure) as "Max Dyastalic Pressure:",
> > >  (select h.dyastalic_pressure
> > >   from health h
> > >   where date between now() - interval '1 week' and now()
> > >   group by h.dyastalic_pressure
> > >   order by count(h.dyastalic_pressure) desc, h.dyastalic_pressure
> > >   limit 1) as "Mode Dyastalic Pressure:",
> > >  count(pulse) as "Pulse Sample Size:",
> > >  round(avg(pulse),1) as "Average Pulse:",
> > >  min(pulse) as "Min Pulse:",
> > >  max(pulse) as "Max Pulse:",
> > >  (select h.pulse
> > >   from health h
> > >   where date between now() - interval '1 week' and now()
> > >   group by h.pulse
> > >   order by count(h.pulse) desc, h.pulse
> > >   limit 1) as "Mode Pulse:",
> > >  count(blood_sugar) as "Sugar Sample Size:",
> > >  round(avg(blood_sugar),1) as "Average Sugar:",
> > >  min(blood_sugar) as "Min Sugar:",
> > >  max(blood_sugar) as "Max Sugar:",
> > >  (select h.blood_sugar
> > >   from health h
> > >   where date between now() - interval '1 week' and now()
> > >   group by h.blood_sugar
> > >   order by count(h.blood_sugar) desc, h.blood_sugar
> > >   limit 1) as "Mode Sugar:"
> > > from health
> > > where date between now() - interval '1 week' and now()
> > > 
> > > union all
> > > 
> > > select
> > >  to_char(date, 'Day') as Title,
> > >  date as "Starting Date:",
> > >  date as "Ending Date:",
> > >  count(cystalic_pressure) as "Cystalic Sample Size:",
> > >  round(avg(cystalic_pressure),1) as "Average Cystalic Pressure:",
> > >  min(cystalic_pressure) as "Min Cystalic Pressure:",
> > >  max(cystalic_pressure) as "Max Cystalic Pressure:",
> > >  (select h.cystalic_pressure
> > >   from health h
> > >   where h.date = health.date
> > >   group by h.cystalic_pressure
> > >   order by count(h.cystalic_pressure) desc, h.cystalic_pressure
> > >   limit 1) as "Mode Cystalic Pressure:",
> > >  count(dyastalic_pressure) as "Dyastalic Sample Size:",
> > >  round(avg(dyastalic_pressure),1) as "Average Dyastalic
> > > Pressure:", min(dyastalic_pressure) as "Min Dyastalic Pressure:",
> > >  max(dyastalic_pressure) as "Max Dyastalic Pressure:",
> > >  (select h.dyastalic_pressure
> > >   from health h
> > >   where h.date = health.date
> > >   group by h.dyastalic_pressure
> > >   order by count(h.dyastalic_pressure) desc, h.dyastalic_pressure
> > >   limit 1) as "Mode Dyastalic Pressure:",
> > >  count(pulse) as "Pulse Sample Size:",
> > >  round(avg(pulse),1) as "Average Pulse:",
> > >  min(pulse) as "Min Pulse:",
> > >  max(pulse) as "Max Pulse:",
> > >  (select h.pulse
> > >   from health h
> > >   where h.date = health.date
> > >   group by h.pulse
> > >   order by count(h.pulse) desc, h.pulse
> > >   limit 1) as "Mode Pulse:",
> > >  count(blood_sugar) as "Sugar Sample Size:",
> > >  round(avg(blood_sugar),1) as "Average Sugar:",
> > >  min(blood_sugar) as "Min Sugar:",
> > >  max(blood_sugar) as "Max Sugar:",
> > >  (select h.blood_sugar
> > >   from health h
> > >   where h.date = health.date
> > >   group by h.blood_sugar
> > >   order by count(h.blood_sugar) desc, h.blood_sugar
> > >   limit 1) as "Mode Sugar:"
> > > from health
> > > where date >= now() - interval '1 week'
> > > group by date
> > > order by "Starting Date:", Title;
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Blinux-list mailing list
> > > Blinux-list@redhat.com
> > > https://www.redhat.com/mailman/listinfo/blinux-list
> > > 
> > > 
> > 
> > jude <jdashiel@shellworld.net>
> > Twitter: @jdashiel
> > 
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
> 
> 

jude <jdashiel@shellworld.net>
Twitter: @jdashiel

Re: sql query

[Shlomi Fish]

Hi Jude,

On Mon, 5 May 2014 18:36:33 -0400 (EDT)
Jude DaShiell <jdashiel@shellworld.net> wrote:

> I wrote a query in sql using psql for an interactive environment in 
> console mode.  I can get a couple different kinds of output neither of 
> which would be useful for production level work.  

You should be using the PostgreSQL API for a language like
Python, Perl, Ruby, etc. and write a wrapper around it in that language and
write custom output. See for example:

* https://metacpan.org/pod/DBD::Pg

The psql tool is meant for interactive use by
developers and its output is not very customisable or usable.

Regards,

	Shlomi Fish

-- 
-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
My Favourite FOSS - http://www.shlomifish.org/open-source/favourite/

Judaism: God is all the shit, all the non‐shit and all the intermediate
demi‐shits in between.

Please reply to list if it's a mailing list post - http://shlom.in/reply .

Re: sql query

[Jude DaShiell]

So that's why all those perl database interfaces in cpan, gdbm mysql and 
postgresql at best are low level tools.  Thanks for the heads up!

On Tue, 6 May 2014, Shlomi Fish wrote:

> Hi Jude,
> 
> On Mon, 5 May 2014 18:36:33 -0400 (EDT)
> Jude DaShiell <jdashiel@shellworld.net> wrote:
> 
> > I wrote a query in sql using psql for an interactive environment in 
> > console mode.  I can get a couple different kinds of output neither of 
> > which would be useful for production level work.  
> 
> You should be using the PostgreSQL API for a language like
> Python, Perl, Ruby, etc. and write a wrapper around it in that language and
> write custom output. See for example:
> 
> * https://metacpan.org/pod/DBD::Pg
> 
> The psql tool is meant for interactive use by
> developers and its output is not very customisable or usable.
> 
> Regards,
> 
> 	Shlomi Fish
> 
> -- 
> -----------------------------------------------------------------
> Shlomi Fish       http://www.shlomifish.org/
> My Favourite FOSS - http://www.shlomifish.org/open-source/favourite/
> 
> Judaism: God is all the shit, all the non?shit and all the intermediate
> demi?shits in between.
> 
> Please reply to list if it's a mailing list post - http://shlom.in/reply .
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

jude <jdashiel@shellworld.net>

Re: sql query

[Geoff Shang]

Hi,

The psql tool, like the mysql tool, are meant for database admins etc. 
They are not intended for generating output for end users.

These databases are intended for use with programming languages.  There 
are PostgreSQL libraries for pretty much any language you care to name. 
These will return results in  a programatic fashion, such as an array or 
list of dictionaries. You can examine the results in your program and 
present the output in any way you choose.

Geoff.