-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more request examples #192
Closed
Closed
Changes from 5 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a74d255
Rename example ozo_request -> ozo_request_coroutine
elsid 8dc86aa
Use a function to run example docker-compose
elsid 2cc7417
Add missing examples to run script
elsid 6bc6286
Add request example with future
elsid 0e583ee
Add request example with callback
elsid 5de4851
Use unique_ptr for result
elsid 7909881
Merge branch 'master' into request_examples
elsid File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
#include <ozo/connection_info.h> | ||
#include <ozo/request.h> | ||
#include <ozo/shortcuts.h> | ||
|
||
#include <boost/asio/io_service.hpp> | ||
|
||
#include <iostream> | ||
|
||
namespace asio = boost::asio; | ||
|
||
int main(int argc, char **argv) { | ||
std::cout << "OZO request example" << std::endl; | ||
|
||
if (argc < 2) { | ||
std::cerr << "Usage: " << argv[0] << " <connection string>\n"; | ||
return 1; | ||
} | ||
|
||
// Ozo perform all IO using Boost.Asio, so first thing we need to do is setup asio::io_context | ||
asio::io_context io; | ||
|
||
// To make a request we need to make a ConnectionSource. It knows how to connect to database using | ||
// connection string. See https://www.postgresql.org/docs/9.4/static/libpq-connect.html#LIBPQ-CONNSTRING | ||
// how to make a connection string. | ||
auto conn_info = ozo::connection_info(argv[1]); | ||
|
||
// Request result is always set of rows. Client should take care of output object lifetime. | ||
const auto result = std::make_shared<ozo::rows_of<int>>(); | ||
|
||
// All IO is asynchronous, therefore we have a choice here, what should be our CompletionToken. | ||
// We use callback function that will be called after operation is finished. | ||
const auto callback = [result] (ozo::error_code ec, auto connection) { | ||
// When request is completed we check is there an error. This example should not produce any errors | ||
// if there are no problems with target database, network or permissions for given user in connection | ||
// string. | ||
if (ec) { | ||
std::cout << "Request failed with error: " << ec.message(); | ||
// Here we should check if the connection is in null state to avoid UB. | ||
if (!ozo::is_null_recursive(connection)) { | ||
// Let's check libpq native error message and if so - print it out | ||
if (auto msg = ozo::error_message(connection); !msg.empty()) { | ||
std::cout << ", error message: " << msg; | ||
} | ||
// Sometimes libpq native error message is not enough, so let's check | ||
// the additional error context from OZO | ||
if (auto ctx = ozo::get_error_context(connection); !ctx.empty()) { | ||
std::cout << ", error context: " << ctx; | ||
} | ||
} | ||
std::cout << std::endl; | ||
return; | ||
} | ||
|
||
// Just print request result | ||
std::cout << "Selected:" << std::endl; | ||
for (auto value : *result) { | ||
std::cout << std::get<0>(value) << std::endl; | ||
} | ||
}; | ||
|
||
// This allows to use _SQL literals | ||
using namespace ozo::literals; | ||
using namespace std::chrono_literals; | ||
ozo::request(conn_info[io], "SELECT 1"_SQL, 1s, ozo::into(*result), callback); | ||
|
||
io.run(); | ||
|
||
return 0; | ||
} |
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
#include <ozo/connection_info.h> | ||
#include <ozo/request.h> | ||
#include <ozo/shortcuts.h> | ||
|
||
#include <boost/asio/io_service.hpp> | ||
#include <boost/asio/use_future.hpp> | ||
|
||
#include <iostream> | ||
#include <thread> | ||
|
||
namespace asio = boost::asio; | ||
|
||
int main(int argc, char **argv) { | ||
std::cout << "OZO request example" << std::endl; | ||
|
||
if (argc < 2) { | ||
std::cerr << "Usage: " << argv[0] << " <connection string>\n"; | ||
return 1; | ||
} | ||
|
||
// Ozo perform all IO using Boost.Asio, so first thing we need to do is setup asio::io_context | ||
asio::io_context io; | ||
|
||
// To make a request we need to make a ConnectionSource. It knows how to connect to database using | ||
// connection string. See https://www.postgresql.org/docs/9.4/static/libpq-connect.html#LIBPQ-CONNSTRING | ||
// how to make a connection string. | ||
auto conn_info = ozo::connection_info(argv[1]); | ||
|
||
// All IO is asynchronous, therefore we have a choice here, what should be our CompletionToken. | ||
// We use boost::asio::use_future. To make this example more real all asynchronous operation will be performed | ||
// in a separate thread. Work guard will help to keep io_context running until we decide to stop it. | ||
boost::asio::executor_work_guard<boost::asio::io_context::executor_type> guard = boost::asio::make_work_guard(io); | ||
std::thread worker([&io] { | ||
io.run(); | ||
}); | ||
|
||
// Request result is always set of rows. Client should take care of output object lifetime. | ||
ozo::rows_of<int> result; | ||
|
||
// This allows to use _SQL literals | ||
using namespace ozo::literals; | ||
using namespace std::chrono_literals; | ||
auto connection = ozo::request(conn_info[io], "SELECT 1"_SQL, 1s, ozo::into(result), asio::use_future); | ||
|
||
// When request is completed we check is there an exception. This example should not produce any errors | ||
// if there are no problems with target database, network or permissions for given user in connection | ||
// string. | ||
try { | ||
// Here we wait until asynchronous operation in a different thread is finished. If any error is occured | ||
// an exception will be thrown. Unfortunately without any additional context, only static error code message. | ||
connection.get(); | ||
|
||
// Just print request result | ||
std::cout << "Selected:" << std::endl; | ||
for (auto value : result) { | ||
std::cout << std::get<0>(value) << std::endl; | ||
} | ||
} catch (const std::exception& error) { | ||
std::cout << "Request failed with error: " << error.what(); | ||
} | ||
|
||
// Reset work guard to release io and make it able to stop. | ||
guard.reset(); | ||
|
||
// Make sure thread is finished. | ||
worker.join(); | ||
|
||
return 0; | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The callback may be a functional object with the result stored as
std::unique_ptr
. Ozo now works fine with non-copyable callbacks.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done