forked from schwigon-aws/Tapper-Benchmark
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Keep track of freestyle changes #1
Open
renormalist
wants to merge
80
commits into
tapper:freestyler
Choose a base branch
from
benchmarkanything:master
base: freestyler
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Basically all =over's were unclosed, missing =back. Fixed that.
The items seemed to look like a numbered list but in fact meant the two hashes to be provided. Reowrd this to use '1st hash' and '2nd hash' making it less confusing.
...so we can automatically correlate the correct file.
...so they get available using File::ShareDir, like for creating the DB with cmdline tools.
Basically copy'n'pasted from ::Query::mysql, and replaced NOW() with CURRENT_TIMESTAMP. More changes are expected to come while reverse engineering how SQLite differs from MySQL... :-)
...in order to find the bug on SQLite: no such column: bav2.bench_additional_value
- Initial release - CPAN DAY - 2015-08-16 - based on the released code from early 2014 - This is a library to provide a schema for storing benchmark values in an SQL database - Primarily targets mysql, SQLite support is basically so far by cutting away known trouble maker SQL statement parts - Read more about the schema on http://benchmarkanything.org/
...to allow ultimate precision.
This avoids the error DBD::SQLite::db prepare failed: no such column: bav2.bench_additional_value at .../Tapper/Benchmark/Query.pm probably by correctly using the SQLite pragmas full_column_names short_column_names which at least can be configured to reproduce the error in plain sqlite3 (though I don't have proof that this is the ultimate solution to that problem).
For key=value pairs where the key is undefined we skip the whole pair. I am not sure it makes sense but I need to avoid db errors resulting from that.
When we insert similar entries it used to insert similar fields and failed. Trying to fix this with simple INSERT IGNORE statements, for mysql and SQLite respectively.
For some reason it seems to Just Work(tm) in SQLite. Let's see if explicitely updating the last inserted id in mysql does the Right Thing.
Quite some code duplication but we are in stupid extension mode, refactoring later this week.
I am not exactly sure if this could be nested but anyway we push/pop the old values so at least that part works nested.
Currently this only covers the cleanup of the queued and already processed raw_bench_bundle rows, but other cleanup can be handled here, too.
When run with the same dbh and the queuing code running with transactions, it seems the garbage collection also needs transactions.
Nested transactions don't work anyway, so the use of a queue with push and pop was over-engineered. Drop it to just setting a single old value.
Be crisp about UNSIGNED and use BLOB to never hit any column limits, just in case...
...when all raw_bench_bundles are processed.
...and replace given/when with classic if/elsif/else cascades.
...to save cpu cycles and let this handle the database.
...into a ::common.pm class.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an experimental PR to track the changes of which I know are forked from the original reality.