perhaps this helps
> -----Original Message-----
> From: pgsql-bugs-owner(at)postgresql(dot)org
> [mailto:pgsql-bugs-owner(at)postgresql(dot)org] On Behalf Of vha
> Sent: Sunday, February 10, 2008 7:55 PM
> To: pgsql-bugs(at)postgresql(dot)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(at)hotmail(dot)com
> PostgreSQL version: 8.3
> Operating system: Windows XP SP2
> Description: SELECT ... WHERE Param = ? does not work
> if Param is of
> type bytea
> 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.
> ---------------------------(end of
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org
> so that your
> message can get through to the mailing list cleanly
In response to
pgsql-bugs by date
|Next:||From: Alvaro Herrera||Date: 2008-02-11 02:22:53|
|Subject: Re: BUG #3948: date/time functions returning wrong value|
|Previous:||From: Tom Lane||Date: 2008-02-10 20:18:35|
|Subject: Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size" |