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.

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

Save in-memory db to disk after all #215

Closed
hannes opened this issue Jun 21, 2019 · 1 comment
Closed

Save in-memory db to disk after all #215

hannes opened this issue Jun 21, 2019 · 1 comment

Comments

@hannes
Copy link
Member

hannes commented Jun 21, 2019

Allow for persisting a in-memory db, aka 'i changed my mind', aka save()

@hannes
Copy link
Member Author

hannes commented Sep 4, 2019

not now

@hannes hannes closed this as completed Sep 4, 2019
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue May 31, 2023
Use overflow testing for timestamp_t arithmetic.
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Jun 1, 2023
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Jun 1, 2023
Catch offset parse overflow errors.
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Jun 3, 2023
Disable coverage of unused functions.
Mytherin added a commit that referenced this issue Jun 5, 2023
Fuzzer #215: Timestamp Arithmetic Overflow
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Sep 7, 2023
* Only use parallel scans for ordered partitions - otherwise the results can be very non-deterministic.
* Make some tests use complete orderings so the expecteds continue to match.
* Disable vector size 2 for moving MODE until we can determine the problem
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Sep 7, 2023
The frame difference loops only work if the frames overlap.
Mytherin added a commit that referenced this issue Sep 7, 2023
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Sep 17, 2023
Cleanup up QUANTILE a bit in preparation for composite frames.
This reduces the problem to generalising ReuseIndexes (future work).
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Sep 17, 2023
Convert ReuseIndexes to handle multiple ranges.
Only tested for single range.
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Sep 17, 2023
Reduce the insert range of Reuse to the current frames
instead of the union of current and previous frames.
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Sep 17, 2023
Back out range restriction.
Add median tests.
hawkfish pushed a commit to hawkfish/duckdb that referenced this issue Oct 2, 2023
Add sorting to handle new work stealing.
hawkfish added a commit to hawkfish/duckdb that referenced this issue Oct 5, 2023
Incorporate review feedback.
Most notably, the ValidityMask object is smart enough to handle
the AllValid situation without constructing extra bitmasks.
Mytherin added a commit that referenced this issue Oct 16, 2023
Internal #215: Window EXCLUDE Functionality
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant