Re: Wired behaviour from SELECT

2024-11-23 Thread Arbol One
Yes! Absolutely true. Thanks for the advice 🙂 On 2024-11-22 3:36 p.m., Ron Johnson wrote: On Fri, Nov 22, 2024 at 3:07 PM Arbol One wrote: Two different SELECT sql statement don't behave the same way. The below sql statement produces the right output SELECT nickname, password FROM

Re: Wired behaviour from SELECT

2024-11-23 Thread Arbol One
Oops! I am putting too many hours in front of the computer, better take a break 😳 On 2024-11-22 3:12 p.m., David G. Johnston wrote: On Fri, Nov 22, 2024 at 1:07 PM Arbol One wrote: The below sql statement produces the right output SELECT nickname, password FROM password WHERE id='09381

Re: Wired behaviour from SELECT

2024-11-22 Thread David Mullineux
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, wrote: > On Fri, Nov 22, 2024 at 1:07 PM Arbol One wrote: > >> The below sql statement produces the right output >> SELECT nickname, password FROM

Re: Wired behaviour from SELECT

2024-11-22 Thread Ron Johnson
On Fri, Nov 22, 2024 at 3:07 PM Arbol One 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 > -+-- > Picc

Re: Wired behaviour from SELECT

2024-11-22 Thread David G. Johnston
On Fri, Nov 22, 2024 at 1:07 PM Arbol One 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 produc