This is how Oracle does it. The equivalent data type to BYTEA in Oracle is RAW. You can use a host variable to specify the length as well.
EXEC SQL BEGIN DECLARE SECTION; unsigned char *bytea_hostvar; EXEC SQL VAR bytea_hostvar IS RAW(1024); EXEC SQL END DECLARE SECTION; ANSI SQL 92 specifies the BIT [VARYING] type, but no mention of a byte data type. ANSI SQL 92, section 11.28, specifies a <character set definition> CREATE CHARACTER SET.... You might be able to shoehorn raw bytes in with that, but it wouldn't be very intuitive, to say the least. It doesn't solve the basic problem of conveying a buffer size to the embedded language parser for a data type without a length specified in the schema. I ended up using Postgres' BIT data type, which works just fine, but really expands the data passed between client and server. From: Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> To: Rick Levine <richard_d_lev...@raytheon.com> Cc: pgsql-bugs@postgresql.org Date: 06/23/2009 04:09 AM Subject: Re: [BUGS] BUG #4866: ECPG and BYTEA Rick Levine wrote: > ECPG does not handle BYTEA columns properly. When I encode a unsigned char > array using PQescapeByteaConn and send it to the server, it is not stored as > the original bytes, but rather is stored as the escaped string (much > larger). Yeah, that's clearly not the right way to do it. You could just use libpq PGExecParams for those queries. I understand that you'd want to stick to the ECPG way of doing things, but that's a good work-around. > We know the coder knows the size of the buffer, but ECPG doesn't, so the > best solution (to my mind) would be to allow the coder to tell ECPG the > buffer size directly. A clean way to do this would be to allow an indicator > variable containing the size, e.g. > > EXEC SQL BEGIN DECLARE SECTION; > unsigned char bytea_hostvar[1024]; > int hostvar_ind = 1024; > EXEC SQL END DECLARE SECTION; > > EXEC SQL AT :connection INSERT INTO Btable > (index, bytea_col) > VALUES > (:index_var, :bytea_hostvar:hostvar_ind); > > I'm just sayin... ;) Yeah, that seems like a clean way to do it. Any idea how this is done in other databases with embedded C support, like DB2 / Informix? Or SQL spec, if it has anything to say about this. It would be good to stay compatible. (I've added this to the TODO list) -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com The following line is added for your protection and will be used for analysis if this message is reported as spam: (Raytheon Analysis: IP=64.18.2.219; e-from=heikki.linnakan...@enterprisedb.com; from=heikki.linnakan...@enterprisedb.com; date=Jun 23, 2009 8:09:36 AM; subject=Re: [BUGS] BUG #4866: ECPG and BYTEA)
