Broollie

> When you send prepared statement parameters with libpq, all parameters are converted once into strings. If you only write `$1` in the SQL, PostgreSQL will treat it as a...

> Oops, and I'm only just trying to catch up! Thanks once again @tt4g for jumping in. > > It looks to me here as if you're using `DataSize` for...

Upon further investigation, i found out that PQXX_HAVE_CONCEPTS was not defined, so now I wonder if there are other defines, that may be missing and, if defined, should enable direct...

@jtv Ok, i ve figured out what s going on. Mostly. So, basically in my main project i build libpqxx with cmake and all defines are present there. But for...

But it also seems like I m missing something, because direct call to `pqxx::string_traits::size_buffer(OkData)` results in linkage error for `pqxx::oops_forbidden_conversion()`, which is not a great sign

> By the way beware that `esc_bin` and `binary_cast` do entirely different things! The former _converts binary data to SQL text format._ The latter merely _creates a view from a...

That is indeed a clash of 2 while not completely different, but still contradicting concepts. There are enough ways of resolving this conflict while keeping backward compatibility (or you can...

@jtv sure, we can just keep the issue open so that you can return to it once you r done

Seems to be a reasonable test case and perhaps there should be a test for a `std::span` as well. Godspeed on the v8.0