Hi,
at work, I am currently upgrading soci from 3.2.2 to 4.0.3. We use
Postgres and SQLITE. The postgres backend behaved somewhat unexpected
when retrieving binary data. I looked into the way SOCI interacts with
the PQ library.
We store binary data (images) in our db. Postgres uses bytea format for
respective columns. The postgres backend requests all data as text.
E.g., assume we have a bytea column which contains the value 42. When
requesting binary format, the query result contains the value 42. For
text queries, it would contain something like {'4', '2'}.
Is there a reason why the postgres backend does only text queries and
then parses the text accordingly? If I were to exchange it for binary
queries, are there any pitfalls besides endianness?
If there aren't, I would fork, fix and create a PR, though I cannot
promise a date when I will be finished.
Wolfgang
_______________________________________________
soci-devel mailing list
soci-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/soci-devel
