-
Notifications
You must be signed in to change notification settings - Fork 183
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
[WIP] feature/table-from-postgresl-sqlite #1453
base: branch-21.06
Are you sure you want to change the base?
[WIP] feature/table-from-postgresl-sqlite #1453
Conversation
…ahuasi/blazingsql into feature/table-from-postgresl-sqlite
…o avoid overlapping
…le-from-postgresl-sqlite
…/blazingsql into feature/table-from-postgresl-sqlite
}; | ||
|
||
TableInfo ExecuteTableInfo(PGconn *connection, const sql_info &sql) { | ||
PGresult *result = PQexec(connection, MakeQueryForColumnsInfo(sql).c_str()); | ||
inline TableInfo ExecuteTableInfo(PGconn * connection, const sql_info & sql) { |
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.
why is this inline?
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.
@williamBlazing, all SQL-providers have a function to get a list columns of the table used to load the data.
So, a TableInfo
contains the list of columns and their data types (to be parsed)
run tests |
Please update the changelog in order to start CI tests. View the gpuCI docs here. |
run tests |
Related #1443