Skip to content

Conversation

@Strech
Copy link
Owner

@Strech Strech commented Nov 26, 2023

As a partial resolution to the logical types conversion, we are going to start with just decoding as the easiest to implement because we already control the decoder hooks.

Resolves #109

@Strech Strech added feature Something new to build internal API Anything related to the internal API and implementations configuration Configuration option of the library labels Nov 26, 2023
@Strech Strech force-pushed the add-logical-types-conversion branch from 3b55613 to e3866a0 Compare November 26, 2023 21:18
@Strech Strech changed the title Add logical types decoding [PROTOTYPE] Add logical types decoding Jul 17, 2024
@Hanspagh
Copy link

Hi @Strech
Do you have plans for merging these changes in? We are currently battling with parsing logical decimal types and it looks like this change would solve this along with a bunch of other nice to haves.

@Strech
Copy link
Owner Author

Strech commented Jun 17, 2025

Hey @Hanspagh I don't have a priority over my prototype PRs for now, but it may come eventually. This is very rough and unfinished work so far with lots of issues to consider (still).

@Hanspagh
Copy link

That is totally fair, let me know if you want any help getting this shipped.

@Strech
Copy link
Owner Author

Strech commented Jun 20, 2025

@Hanspagh I will not promise anything, but I plan to work on it one day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

configuration Configuration option of the library feature Something new to build internal API Anything related to the internal API and implementations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

logicalType: date

3 participants