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.

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

CASSGO-36 could map scan get nil instead of zero value for null value #1834

Open
wants to merge 3 commits into
base: trunk
Choose a base branch
from

Conversation

OleksiienkoMykyta
Copy link
Contributor

Closes #1699

This PR adds a new feature (MapScanWithNullableValues) that allows users to receive nullable values from Cassandra.

@joao-r-reis joao-r-reis changed the title Issue-1699, could map scan get nil instead of zero value for null value CASSGO-36 could map scan get nil instead of zero value for null value Nov 20, 2024
@jameshartig
Copy link
Contributor

Based on this being possible outside of the package I'm hesitant to approve this. See my comment on the original issue: #1699 (comment)

@OleksiienkoMykyta
Copy link
Contributor Author

@jameshartig I believe we should consider implementing features directly within gocql rather than requiring external solutions. It would be much more convenient to have these features available out of the box. Furthermore, it seems like this behavior should be the default since Cassandra can return nullable values. Currently, gocql represents these as default Go values, which alters the original data. To address this, we should at least provide an alternative functionality that preserves the original data and aligns with Cassandra's behavior.

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.

CASSGO-36 Could MapScan() get nil instead of zero value for null value?
2 participants