Re: BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea - Mailing list pgsql-bugs

From Gevik Babakhani
Subject Re: BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea
Date
Msg-id 000c01c86c31$93ce7e80$0a01a8c0@gevmus
Whole thread Raw
In response to BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea  ("vha" <vincent_dhaene@hotmail.com>)
Responses Re: BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea  (Vincent D'Haene <vincent_dhaene@hotmail.com>)
List pgsql-bugs
perhaps this helps

http://www.webservertalk.com/archive308-2007-3-1836413.html


> -----Original Message-----
> From: pgsql-bugs-owner@postgresql.org
> [mailto:pgsql-bugs-owner@postgresql.org] On Behalf Of vha
> Sent: Sunday, February 10, 2008 7:55 PM
> To: pgsql-bugs@postgresql.org
> Subject: [BUGS] BUG #3951: SELECT ... WHERE Param = ? does
> not work if Param is of type bytea
>
>
> The following bug has been logged online:
>
> Bug reference:      3951
> Logged by:          vha
> Email address:      vincent_dhaene@hotmail.com
> PostgreSQL version: 8.3
> Operating system:   Windows XP SP2
> Description:        SELECT ... WHERE Param = ? does not work
> if Param is of
> type bytea
> Details:
>
> I have a table with one of the columns of type BYTEA
> containing GUIDs (16 bytes of data).
>
> The data of the column is specified using
> SQLBindParameter(hstmt, nCol, SQL_PARAM_INPUT, SQL_C_BINARY,
> SQL_BINARY, 16, 0, theGUID, 16, &ptr).
>
> This works fine to insert the data using "INSERT ... VALUES
> ?", but retrieving the data using "SELECT ... WHERE Param =
> ?" doesn't work: nothing is returned.
>
> Am I doing something wrong or is this a bug?
>
> BTW. This code works without any problem on MS SQL 2000, MS
> SQL 2005, Oracle and MySQL.
>
>
> vha
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org
> so that your
>        message can get through to the mailing list cleanly
>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #3948: date/time functions returning wrong value