You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Guidance
Bug reports are for when HammerDB is not behaving as expected.
Bug reports should not be submitted for help in understanding database performance related questions.
General questions on database performance or HammerDB usability should be submitted under Discussions.
Describe the bug
A clear and concise description of what the bug is.
set the bm to tpc-h and set the db to mysql, run the buildschema, it will through out error and stop
To Reproduce
Steps to reproduce the behavior:
mysql->tpc-h->buildschema
Go to '...'
Click on '....'
Run workload '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
HammerDB Version (please complete the following information):
Version: [e.g. 4.7]
Build: [e.g. Release download or build from source]
4.8 HammerDB Interface (please complete the following information):
UI: [e.g. GUI or CLI]
CLI Operating System (please complete the following information):
Server OS: [e.g. RHEL8]
Client OS: [e.g. Windows 11]
RHEL8 Database Server (please complete the following information):
Database name: [e.g. PostgreSQL]
Database Release Version [e.g. 15.2]
Database Client (please complete the following information):
Database client name: [e.g. ODBC Driver 18 for SQL Server]
Additional context
Add any other context about the problem here.
I check the source it's due to inconsistent data type in src/mysql/mysqlolap.tcl line 188 as below
188 L_ORDERKEY BIGINT NOT NULL,
different with line 105
105 O_ORDERKEY INT NOT NULL,
The text was updated successfully, but these errors were encountered:
Guidance
Bug reports are for when HammerDB is not behaving as expected.
Bug reports should not be submitted for help in understanding database performance related questions.
General questions on database performance or HammerDB usability should be submitted under Discussions.
Describe the bug
A clear and concise description of what the bug is.
set the bm to tpc-h and set the db to mysql, run the buildschema, it will through out error and stop
To Reproduce
Steps to reproduce the behavior:
mysql->tpc-h->buildschema
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
HammerDB Version (please complete the following information):
4.8
HammerDB Interface (please complete the following information):
CLI
Operating System (please complete the following information):
RHEL8
Database Server (please complete the following information):
Database Client (please complete the following information):
Additional context
Add any other context about the problem here.
I check the source it's due to inconsistent data type in src/mysql/mysqlolap.tcl line 188 as below
188 L_ORDERKEY BIGINT NOT NULL,
different with line 105
105
O_ORDERKEY
INT NOT NULL,The text was updated successfully, but these errors were encountered: