Thread: Wired behaviour from SELECT

Oops!
I am putting too many hours in front of the computer, better take a break 😳

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.

Yes! Absolutely true. Thanks for the advice 🙂

On Fri, Nov 22, 2024 at 3:07 PM Arbol One <arbolone@hotmail.ca> wrote:

Two different SELECT sql statement don't behave the same way.

The below sql statement produces the right output
SELECT nickname, password FROM password WHERE id='0938105618107N1';
  nickname   | password
-------------+----------
 Piccard@@21 |  Arbol
(1 row)

Storing passwords in plain text is the Worst Possible Security Practice Ever Conceived.

--

Death to <Redacted>, and butter sauce.

Don't boil me, I'm still alive.

<Redacted> lobster!