testing: adding catalog api and large table fetch benchmark testcase#1561
testing: adding catalog api and large table fetch benchmark testcase#1561Anshu6250 wants to merge 4 commits into
Conversation
| ASSERT_EQ(Connect(connection_string, conn), SQL_SUCCESS) << "Failed to connect to the database."; | ||
|
|
||
| // Generate 90 Lakh (9,000,000) rows by cross-joining two arrays of 3,000 | ||
| std::string query = R"( |
There was a problem hiding this comment.
don't do this, utilise the existing tables like kirltest tables for huge data and all_data_types I think exists for all data types
9417f45 to
15288a7
Compare
15288a7 to
f36e919
Compare
| case SQL_FLOAT: | ||
| case SQL_DOUBLE: col_ptr->data_type = SQL_C_DOUBLE; break; | ||
| case SQL_BIT: col_ptr->data_type = SQL_C_BIT; break; | ||
| default: col_ptr->data_type = SQL_C_CHAR; break; |
There was a problem hiding this comment.
have cases for other data types as well like date, time, numeric, range
| DescribeCol(conn, col_ptr, i); | ||
|
|
||
| switch (col_ptr->data_type) { | ||
| case SQL_BIGINT: |
There was a problem hiding this comment.
same here have cases for other data types as well like date, time, numeric, range
| TEST(DataFetchPerformance, Benchmark_PowerBI_Mimic_NewTimestampTable) { | ||
| auto conn = std::make_shared<ODBCHandles>(); | ||
|
|
||
| std::string connection_string = kDefaultConnectionString + ";AllowHtapiForLargeResults=1;HTAPI_ActivationThreshold=0;"; |
There was a problem hiding this comment.
make all test cases parametrized and run with htapi and without
| DescribeCol(conn, col_ptr, i); | ||
|
|
||
| switch (col_ptr->data_type) { | ||
| case SQL_BIGINT: |
There was a problem hiding this comment.
instead of doing this , use SqlToCdataTypes(col_ptr) instead , as here we are not doing conversion simply returning as string, maybe can have a separate test case to bind with SQL_C_CHAR only
c2a572d to
a21251d
Compare
a21251d to
c73f564
Compare
|
|
@Anshu6250 In this PR, create the cmake target only. We can make the CI changes in the next one. |
| break; | ||
| case SQL_VARCHAR: | ||
| case SQL_CHAR: | ||
| case SQL_NUMERIC: |
There was a problem hiding this comment.
why are we returning SQL_NUMERIC and SQL_DECIMAL as SQL_C_CHAR ?
No description provided.