Re: Wired behaviour from SELECT

From: David Mullineux <dmullx(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Arbol One <arbolone(at)hotmail(dot)ca>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, PostGreSQL MailingList <pgsql-general(at)postgresql(dot)org>
Subject: Re: Wired behaviour from SELECT
Date: 2024-11-22 23:55:30
Message-ID: CAGsyd8WU_FsAJ-DJ0+54iBoJKRWTfVphShHVSig8hcz=7pi4aA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Instead of nickname you probably want tontet where password=`Arbol' .. or
am.i.missong something ?.

On Fri, 22 Nov 2024, 20:13 David G. Johnston, <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Fri, Nov 22, 2024 at 1:07 PM Arbol One <arbolone(at)hotmail(dot)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.
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Arbol One 2024-11-23 09:47:48 Re: Wired behaviour from SELECT
Previous Message Eric Hanson 2024-11-22 23:23:19 Re: Fwd: A million users