Re: PQunescapebytea not reverse of PQescapebytea?
Florian Weimer <[email protected]> Wed, 19 Mar 2014 21:28:07 +0100
| Newsgroups | gmane.comp.db.postgresql.interfaces |
|---|---|
| Message-ID | <[email protected]> |
* Karthik Segpi: > I have a 'bytea' column in the database, onto which my custom C application > is inserting encrypted data. Before inserting, I am calling > 'PQescapebytea()' to escape the ciphertext. However, after SELECT, the data > needs to be 'un-escaped' before attempting to decrypt. I am trying to > 'un-escape' using 'PQunescapebytea'. However, I am finding that > 'PQunescapebytea' is not exact inverse of 'PQescapebytea'. I saw > documentation and posts in the mailing lists alluding to this as well. As a > result, the decryption always fails. Can you show us some example data that shows the inconsistency? PQunescapebytea should give you back the blob you passed to PQescapebytea, but the same blob can have different BYTEA encodings—not everyone uses the \x hexadecimal encoding. -- Sent via pgsql-interfaces mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-interfaces