Skip to content

Commit ffa3f4e

Browse files
lukekimMaxxen
authored andcommitted
Update references to github.com/wangfenjin/duckdb-rs to github.com/duckdb/duckdb-rs
1 parent ef1432f commit ffa3f4e

File tree

3 files changed

+8
-9
lines changed

3 files changed

+8
-9
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ cd ~/github/duckdb-rs/crates/libduckdb-sys
5353
cargo test --features bundled
5454
```
5555

56-
Currently in [github actions](https://github.com/wangfenjin/duckdb-rs/actions), we always use the bundled file for testing. So if you change the header in duckdb-cpp repo, you need to make the PR merged and updated the [bundled-file](https://github.com/wangfenjin/duckdb-rs/tree/main/crates/libduckdb-sys/duckdb).
56+
Currently in [github actions](https://github.com/duckdb/duckdb-rs/actions), we always use the bundled file for testing. So if you change the header in duckdb-cpp repo, you need to make the PR merged and updated the [bundled-file](https://github.com/duckdb/duckdb-rs/tree/main/crates/libduckdb-sys/duckdb).
5757
You can generated the amalgamated file by:
5858

5959
```shell

README.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# duckdb-rs
22

33
[![Downloads](https://img.shields.io/crates/d/duckdb)](https://img.shields.io/crates/d/duckdb)
4-
[![Build Status](https://github.com/wangfenjin/duckdb-rs/workflows/CI/badge.svg)](https://github.com/wangfenjin/duckdb-rs/actions)
4+
[![Build Status](https://github.com/duckdb/duckdb-rs/workflows/CI/badge.svg)](https://github.com/duckdb/duckdb-rs/actions)
55
[![dependency status](https://deps.rs/repo/github/wangfenjin/duckdb-rs/status.svg)](https://deps.rs/repo/github/wangfenjin/duckdb-rs)
66
[![codecov](https://codecov.io/gh/wangfenjin/duckdb-rs/branch/main/graph/badge.svg?token=0xV88q8KU0)](https://codecov.io/gh/wangfenjin/duckdb-rs)
77
[![Latest Version](https://img.shields.io/crates/v/duckdb.svg)](https://crates.io/crates/duckdb)
@@ -15,7 +15,7 @@ forked from rusqlite as duckdb also tries to expose a sqlite3 compatible API.
1515
use duckdb::{params, Connection, Result};
1616

1717
// In your project, we need to keep the arrow version same as the version used in duckdb.
18-
// Refer to https://github.com/wangfenjin/duckdb-rs/issues/92
18+
// Refer to https://github.com/duckdb/duckdb-rs/issues/92
1919
// You can either:
2020
use duckdb::arrow::record_batch::RecordBatch;
2121
// Or in your Cargo.toml, use * as the version; features can be toggled according to your needs
@@ -85,7 +85,7 @@ declarations for DuckDB's C API. By default, `libduckdb-sys` attempts to find a
8585

8686
You can adjust this behavior in a number of ways:
8787

88-
* If you use the `bundled` feature, `libduckdb-sys` will use the
88+
- If you use the `bundled` feature, `libduckdb-sys` will use the
8989
[cc](https://crates.io/crates/cc) crate to compile DuckDB from source and
9090
link against that. This source is embedded in the `libduckdb-sys` crate and
9191
as we are still in development, we will update it regularly. After we are more stable,
@@ -97,7 +97,7 @@ You can adjust this behavior in a number of ways:
9797
```
9898

9999
`Cargo.toml` will be updated.
100-
100+
101101
```toml
102102
[dependencies]
103103
# Assume that version DuckDB version 0.9.2 is used.
@@ -110,7 +110,6 @@ You can adjust this behavior in a number of ways:
110110
options. The default when using vcpkg is to dynamically link,
111111
which must be enabled by setting `VCPKGRS_DYNAMIC=1` environment variable before build.
112112

113-
114113
### Binding generation
115114

116115
We use [bindgen](https://crates.io/crates/bindgen) to generate the Rust

crates/duckdb/src/vtab/arrow.rs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,7 @@ pub fn to_duckdb_logical_type(data_type: &DataType) -> Result<LogicalTypeHandle,
220220
| DataType::FixedSizeBinary(_) => Ok(LogicalTypeHandle::from(to_duckdb_type_id(data_type)?)),
221221
dtype if dtype.is_primitive() => Ok(LogicalTypeHandle::from(to_duckdb_type_id(data_type)?)),
222222
_ => Err(format!(
223-
"Unsupported data type: {data_type}, please file an issue https://github.com/wangfenjin/duckdb-rs"
223+
"Unsupported data type: {data_type}, please file an issue https://github.com/duckdb/duckdb-rs"
224224
)
225225
.into()),
226226
}
@@ -636,7 +636,7 @@ pub fn write_arrow_array_to_vector(
636636
}
637637
dt => {
638638
return Err(format!(
639-
"column with data_type {} is not supported yet, please file an issue https://github.com/wangfenjin/duckdb-rs",
639+
"column with data_type {} is not supported yet, please file an issue https://github.com/duckdb/duckdb-rs",
640640
dt
641641
)
642642
.into());
@@ -1071,7 +1071,7 @@ fn struct_array_to_vector(array: &StructArray, out: &mut StructVector) -> Result
10711071
}
10721072
_ => {
10731073
unimplemented!(
1074-
"Unsupported data type: {}, please file an issue https://github.com/wangfenjin/duckdb-rs",
1074+
"Unsupported data type: {}, please file an issue https://github.com/duckdb/duckdb-rs",
10751075
column.data_type()
10761076
);
10771077
}

0 commit comments

Comments
 (0)