Jeroen Vermeulen
Jeroen Vermeulen
OK, I'll keep it in mind as a nice project to do next. Let's rename this ticket from "`pqxx::result` feedback" to "`query` for prepared statements" so I can keep it...
Indeed. I have removed the label. And who knows, I may find some time today to do actual work on this issue.
Thank you @alexolog . Do you have any specific features that make `pqxx::result` useful to your use-cases than streaming queries? Is it mainly about knowing the result size, or perhaps...
> > Thank you @alexolog . Do you have any specific features that make `pqxx::result` useful to your use-cases than streaming queries? Is it mainly about knowing the result size,...
> Mine is a loads stored procs of non streamed data, "prepared statements" , create GIS datasets > that return specfic data fields, also validate exectution of queries, multiple progs...
@alexolog In #773 I extend the documentation for streaming. Hope that answers your questions.
@HackettJP that's cool to hear. I hope some day somebody will publish a library for handling PostGIS data types in libpqxx.
> > Mine is a loads stored procs of non streamed data, "prepared statements" , create GIS datasets > > that return specfic data fields, also validate exectution of queries,...
It's getting a little awkward making up all these different names for very similar functions. What if we had a marker type for prepared functions, and that would be the...
Strange... What's the type of the variable you're passing as the parameter?