Test try ruby asan #3
Open
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
refs: suketaGH-690 In this PR, we add DuckDB::LogicalType#type, which returns logical type's type. - [duckdb_type duckdb_get_type_id(duckdb_logical_type type);](https://duckdb.org/docs/api/c/api.html#duckdb_get_type_id) This is one of the steps for supporting duckdb_logical_column_type C API.
add DuckDB::LogicalType#type
get error from duckdb when Appender#append_int32 failed.
- fix indent - fix call-seq
fix appender rdoc.
try to make documents
fix setup make document yml
change create published branch
fix rdoc files
setup rdoc options
add documentation url.
fix error message of appender_int64
get error message from duckdb when DuckDB::Appender#append_uint8 failed.
change error handling of DuckDB::Appender#append_uint8
Try to fix CI failures of suketa#845 by close and reopen database each test.
try to fix CI failures.
refs: suketaGH-690 In this PR, we add DuckDB::LogicalType#child_type which is the following binding method. ```c duckdb_logical_type duckdb_list_type_child_type(duckdb_logical_type type); ``` ref: https://duckdb.org/docs/api/c/api.html#duckdb_list_type_child_type ref: https://github.com/duckdb/duckdb/blob/main/src/main/capi/logical_types-c.cpp#L226-L236 This is one of the steps for supporting duckdb_logical_column_type C API.
…ical-type logical_type: add `DuckDB::LogicalType#child_type`
update CHANGELOG.md
- CI checks with duckdb 1.2.0. - change duckdb 1.2.0 in Dockerfile.
bump duckdb 1.2.0
DuckDB::Result#row_count, DuckDB::Result#row_size are deprecated. Because duckdb_row_count C-API of duckdb has been removed and may be removed in future versions of DuckDB.
…_count DuckDB::Result#row_count is depreacted
Thease methods don't effect any behavior changes of ruby-duckdb.
…each deprecate DuckDB::Result.use_chunk_each, DuckDB::Result.use_chunk_each?
use duckdb_fetch_chunk because ruby-duckdb supports duckdb >= 1.0.0.
always use duckdb_fetch_chunk
- calling duckdb_destroy_prepare. - rescue StandardError.
This reverts commit 504a919.
otegami
force-pushed
the
test-try-ruby-asan
branch
2 times, most recently
from
5a65638 to
b8efa79
Compare
otegami
force-pushed
the
test-try-ruby-asan
branch
from
b8efa79 to
88e34f6
Compare
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.
No description provided.