-
Notifications
You must be signed in to change notification settings - Fork 489
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
apoc.load.jdbc does not support JDBC array types #3766
Comments
sarmbruster
added a commit
to sarmbruster/neo4j-apoc-procedures
that referenced
this issue
Sep 2, 2023
sarmbruster
added a commit
to sarmbruster/neo4j-apoc-procedures
that referenced
this issue
Sep 2, 2023
vga91
pushed a commit
that referenced
this issue
Dec 19, 2023
vga91
pushed a commit
that referenced
this issue
Dec 19, 2023
vga91
pushed a commit
that referenced
this issue
Dec 19, 2023
vga91
pushed a commit
that referenced
this issue
Dec 19, 2023
vga91
added a commit
that referenced
this issue
Dec 19, 2023
vga91
added a commit
that referenced
this issue
Dec 19, 2023
vga91
pushed a commit
that referenced
this issue
Jan 18, 2024
vga91
added a commit
that referenced
this issue
Jan 23, 2024
vga91
pushed a commit
that referenced
this issue
Jan 24, 2024
vga91
added a commit
that referenced
this issue
Jan 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior (Mandatory)
apoc.load.jdbc should deal gracefully with array columns.
JDBC returns javax.sql.Array for them and they should be mapped to normal arrays.
Some RDBMS, e.g. postgres, do support native array as column types.
Actual Behavior (Mandatory)
getting an error message
Versions
I'll send a PR for this against 4.4 branch in the next days.
The text was updated successfully, but these errors were encountered: