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

Wrong error reported while scanning records when query contains several ordering fields #2041

Open
NVO777 opened this issue Jan 13, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@NVO777
Copy link

NVO777 commented Jan 13, 2025

Error reported while scanning such query: SELECT id, req_primary_fields FROM audit_log ORDER BY created_tstamp DESC, id ASC LIMIT 10 OFFSET 0, Error = Scan error on column index 1, name "req_primary_fields": converting NULL to string is unsupported

No error should happen here, because SELECT COUNT(id) FROM audit_log WHERE req_primary_fields IS NULL returns 0

Not sure would it be possible to reproduce it, but i attached code and log and You can analyze it
ZIP contains:
run_test.sh - how do i run the test
immu.go - Go source file
immu.log - Go test file execution output

test_20250113.zip

Environment

# run "immu* version" and copy/paste the output here

immuclient version
immuclient 1.9.4
Commit : 76cd08a
Built at: Thu, 25 Jul 2024 20:17:12 UTC

Additional info (any other context about the problem)

@NVO777 NVO777 added the bug Something isn't working label Jan 13, 2025
@NVO777
Copy link
Author

NVO777 commented Jan 13, 2025

Attached test_20250113_v2.zip where You can see clearly that after adding second column to the order code fails
test_20250113_v2.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant