This repository was archived by the owner on May 17, 2024. It is now read-only.
Track data-diff usage in MotherDuck #800
Merged
Conversation
This file contains hidden or 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
added 11 commits December 13, 2023 13:46
…racking/motherduck-user-agent
added 2 commits December 18, 2023 12:44
dlawin approved these changes Dec 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
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.
Add data-diff usage tracking to motherduck to understand usage trends and open up partnership opportunities.
Logic Changes
Testing
jaffle_shop.duckdbto work with the latest duckdb version 0.9.2 and replicates the same results before this PR. It was using 0.7.1 that was causing errors when interfacing with motherduck.