Re: Wired behaviour from SELECT - Mailing list pgsql-general

From David G. Johnston
Subject Re: Wired behaviour from SELECT
Date
Msg-id CAKFQuwahNdTb3kHWyDGnxkTqD3oH18tS597y3WKv8UdNz5-xhw@mail.gmail.com
Whole thread Raw
In response to Wired behaviour from SELECT  (Arbol One <arbolone@hotmail.ca>)
Responses Re: Wired behaviour from SELECT
Re: Wired behaviour from SELECT
List pgsql-general
On Fri, Nov 22, 2024 at 1:07 PM Arbol One <arbolone@hotmail.ca> wrote:
The below sql statement produces the right output
SELECT nickname, password FROM password WHERE id='0938105618107N1';
  nickname   | password
-------------+----------
 Piccard@@21 |  Arbol
(1 row)
However, if this sql statement produces the wrong output
SELECT nickname, password FROM password WHERE nickname='Arbol';
 nickname | password
----------+----------
(0 rows)
What am I doing wrong?
Naming a column in your table the same name as the table is problematic generally.  As for the query, if they are both intended to return the same row the value Arbol is in the password column, not the nickname column.  You seem to have reversed the data for the two columns.

David J.

pgsql-general by date:

Previous
From: Arbol One
Date:
Subject: Wired behaviour from SELECT
Next
From: Ron Johnson
Date:
Subject: Re: Wired behaviour from SELECT