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.

Sign up for GitHub

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

Jump to bottom

Migrate to new C API #59

Open
mharrisb1 opened this issue Feb 5, 2025 · 2 comments
Open

Migrate to new C API #59

mharrisb1 opened this issue Feb 5, 2025 · 2 comments

Comments

@mharrisb1
Copy link
Contributor

More of a discussion than issue but what are the thoughts on migrating to new C API announced with v1.2.0?

Would help guarantee a more stable interface to work with and will probably be the way most extensions go in the near future.
@archiewood
Copy link
Member

Agree although I dont know if the new C API will expose all that we need, we reach pretty deep into some of the internals.

I expect easy things to do:

  • register new functions

harder things to do

  • most other stuff

@Alex-Monahan
Copy link
Contributor

I asked the DuckDB Labs team about this a few months back, and at that time the C API did not have the hooks we needed. We can recheck though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mharrisb1 @Alex-Monahan @archiewood