| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | scomp(at)canada(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Going crazy comparing bytea columns |
| Date: | 2006-03-01 21:04:06 |
| Message-ID: | 15238.1141247046@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
scomp(at)canada(dot)com writes:
> I am using npgsql with C# to insert a bytea value into a
> column which will serve as an encrypted password. This works
> well. However, when I retrieve the value, it is different.
> In other words, "select pwd from table where pwd like @pwd"
> does not work.
Why are you using LIKE when you apparently want simple equality?
ISTM that LIKE opens up a whole can of worms with possible appearance
of the wildcards (% and _, not to mention \) in the string.
Another likely source of trouble is that you're not dealing with
escaping of non-ASCII byte values the same way when you insert
the password as when you try to look it up.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2006-03-01 21:14:46 | Re: Going crazy comparing bytea columns |
| Previous Message | Tino Wildenhain | 2006-03-01 20:54:11 | Re: a web framework for postgresql? |