Handle potential columns in type conversion #1186
Unanswered
damian-kos
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How can I handle columns in type conversion which won't always be there?
For example when we add something by JOIN?
I know that I can v.get_number_of_columns() and work around this but this is not flexbile enough.
// if another column which could be added by for example left join model.customer.phone = v.get<std::string>("phone"); // if it doesnt exists in basic query it will fail in type conversion
Beta Was this translation helpful? Give feedback.
All reactions