lganzzzo on better_json
bamkrs on v1.3.0
lganzzzo on master
Add option to link with MSVC st… Make MSVC runtime setting avail… Merge pull request #435 from Ya… (compare)
@oatpp_io_twitter to add the content type header i have to do:
API_CALL("POST", "api/controller.cgi", doPost, BODY_STRING(String, body), HEADER(String, cookie, "Cookie"), HEADER(String, content_type, "Content-Type"))
auto response = client_->doPost("parameter1=example1¶meter2=example2", "sample cookie data", "application/x-www-form-urlencoded");
Hey @sunrongyi ,
dbResult->fetch<oatpp::String>() ； Can I use like this?
No, for a single value you have to do like this:
auto dataset = dbResult->fetch<oatpp::Vector<oatpp::Vector<oatpp::String>>>(); oatpp::String value = dataset;
For more info - see this issue - oatpp/oatpp-sqlite#9
I'm willing to give it another go round! I'll try rebuilding everying tomorrow
Thanks, please let me know if it worked
I also had similar "oddness" in the past with crashes around allocators and the COMPONENT macros. I run Gentoo and it's possible (easy?) to upgrade various parts of the operating system without getting it all done correctly. Something simple such as a minor GCC upgrade sometimes means libraries are hanging around partially built with the new/old compilers as the linker combines things. The postgres library libpqxx is rather sensitive to any differences in the lower level libraries it uses (glibc/gcc/etc) and if you get weird crashes it sometimes is related to simple mismatch or partial compiler upgrade without rebuilding all the downstream libraries.
So maybe this would be resolved simply by double checking the library link consistency (revdep-rebuilld equivalent for other operating systems)