Skip to content

Conversation

@Tom-Sloboda
Copy link
Contributor

@Tom-Sloboda Tom-Sloboda commented Aug 27, 2025

Proposed Changes

Updates DuckDB.NET packages to v1.3.2 to fix build error.

Types of changes

What types of changes does your code introduce to SQLProvider?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • Build and tests pass locally
  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added necessary documentation (if appropriate)

@Thorium
Copy link
Member

Thorium commented Aug 27, 2025

Looks ok to me. Let me know when ok to merge.

Right now it bundles some package updates with the case-sensitivity fix. If it goes too complex, just separate the package updates, we can do those as a separate PR later as well. I remember there was some challenges with e.g. StructureLogger (used in build only) different versions and dependency hierarchies.

@Tom-Sloboda Tom-Sloboda changed the title Release 1.5.13: Fix 2 build isues (Linux and DuckDB) and bump the dependency versions Fix build issues related to DuckDB Aug 27, 2025
@Tom-Sloboda
Copy link
Contributor Author

Split off the Firebird rename into #853

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

Successfully merging this pull request may close these issues.

2 participants