On Mon, 12 Jul 2021, Rich Shepard wrote:
Long ago I wrote a query which was greatly improved (i.e., it actually
worked as intended) by help here):
Ah! It finally came back to me as I looked to revise it. What I want both
&p.lname and &p.fname are specific names passed in from the user. Now I k
On Mon, 12 Jul 2021, Rob Sargent wrote:
Having a hard time seeing the value in p.lname = p.lname and straight sql.
Me, too. That's why I wanted an explanation. Seems to me I added it sometime
for no valid reason. As I've not run that query in a very long time I'll
clean up the query and test i
On Mon, 12 Jul 2021, Adrian Klaver wrote:
You should also follow Tom's suggestion and do:
\do+ &
in psql.
It's the bitwise 'and':
# \do+ &
List of operators
Schema | Name | Left arg type | Right arg type | Result type | Function | Description
-
On 7/12/21 11:47 AM, Rich Shepard wrote:
On Mon, 12 Jul 2021, Rob Sargent wrote:
These look like value substitutions, usually done on the client at it
sends the sql. How is this sql getting to the server (presumably after
substitution).
Rob,
I was running queries from the psql back then. Now
On 7/12/21 10:45 AM, Rich Shepard wrote:
On Mon, 12 Jul 2021, Tom Lane wrote:
AFAICS this is invoking a prefix operator named "&". There is no such
operator built into Postgres. Maybe psql's "\do+ &" would jog your memory
about where yours came from.
tom,
I thought it wasn't part of postgres
On 7/12/21 10:45 AM, Rich Shepard wrote:
On Mon, 12 Jul 2021, Tom Lane wrote:
AFAICS this is invoking a prefix operator named "&". There is no such
operator built into Postgres. Maybe psql's "\do+ &" would jog your memory
about where yours came from.
tom,
I thought it wasn't part of postgres
On Mon, 12 Jul 2021, Rob Sargent wrote:
These look like value substitutions, usually done on the client at it
sends the sql. How is this sql getting to the server (presumably after
substitution).
Rob,
I was running queries from the psql back then. Now I'm adding a GUI
(tkinter) and using psyc
On Mon, 12 Jul 2021, Tom Lane wrote:
AFAICS this is invoking a prefix operator named "&". There is no such
operator built into Postgres. Maybe psql's "\do+ &" would jog your memory
about where yours came from.
tom,
I thought it wasn't part of postgres. I've no idea why it's there, but I'll
re
On 7/12/21 11:25 AM, Rich Shepard wrote:
Long ago I wrote a query which was greatly improved (i.e., it actually
worked as intended) by help here):
/* This query selects all activity information for a named person */
SELECT p.lname, p.fname, p.loc_nbr, p.job_title, p.direct_phone,
p.active,
Rich Shepard writes:
> Long ago I wrote a query which was greatly improved (i.e., it actually
> worked as intended) by help here):
> SELECT ...
> WHERE p.lname = &p.lname AND p.fname = &p.fname;
> I did not save the reason why the ampersand is used in the WHERE row selection
> phrase and want no
Long ago I wrote a query which was greatly improved (i.e., it actually
worked as intended) by help here):
/* This query selects all activity information for a named person */
SELECT p.lname, p.fname, p.loc_nbr, p.job_title, p.direct_phone, p.active,
o.org_name,
l.loc_nbr, l.loc_nam
11 matches
Mail list logo
