Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix faulty INSERT test query from the templated benchmark example introduced in #386 since it results in duplicate keys #428

Open
bpkroth opened this issue Dec 14, 2023 · 3 comments
Open

Fix faulty INSERT test query from the templated benchmark example introduced in #386 since it results in duplicate keys #428

bpkroth opened this issue Dec 14, 2023 · 3 comments

Comments

@bpkroth
Copy link
Collaborator

bpkroth commented Dec 14, 2023

Need to fix INSERT test query from the templated benchmark example introduced in #386 since it results in duplicate keys.

Originally posted by @bpkroth in #427 (comment)
@bpkroth
Copy link
Collaborator Author

bpkroth commented Dec 14, 2023

@ETHenzlere can you please take a look at this?

@bpkroth
Copy link
Collaborator Author

bpkroth commented Dec 14, 2023

@anjagruenheid for visibility

@bpkroth
Copy link
Collaborator Author

bpkroth commented Dec 14, 2023

See Also: 7d4e90b

@bpkroth bpkroth mentioned this issue Dec 19, 2023
Merged
@ETHenzlere ETHenzlere mentioned this issue Jan 5, 2024
Merged
bpkroth pushed a commit that referenced this issue Jan 17, 2024
@ETHenzlere
Fix: Changed INSERT statements of templated benchmarks (#447)
febe379 
INSERT query was not working due to duplicate primary keys

Simple solutions on the query did not work for all systems
(For example _INSERT IGNORE, INSERT -- IF NOT EXISTS_).

For now I changed the table of the insert to one that does not have a
primary key.

This PR tries to solve #428
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bpkroth