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

Use of Blob from result set yields NullPointerException after commit [JDBC587] #618

Closed
firebird-automations opened this issue Jun 22, 2019 · 8 comments

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Using a java.sql.Blob instance from a result set yields a NullPointerException after commit, instead it should yield an error that the blob is not available after commit.

Commits: f9359bb 1d72e6e

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Version: Jaybird 3.0.6 [ 10883 ]

Version: Jaybird 4.0.0-beta-1 [ 10901 ]

Fix Version: Jaybird 4.0.0-beta-2 [ 10902 ]

Fix Version: Jaybird 3.0.7 [ 10910 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

description: Using a java.sql.Blob instance from a result set yields a NullPointerException after commit, instead it should yield an error that the blob is not available after commit. => Using a java.sql.Blob instance from a result set yields a NullPointerException after commit, instead it should yield an error that the blob is not available after commit.

Alternatively, try to start a new transaction and see if the blob id is still valid.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Component: JDBC driver [ 10053 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 4 [ 10441 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

description: Using a java.sql.Blob instance from a result set yields a NullPointerException after commit, instead it should yield an error that the blob is not available after commit.

Alternatively, try to start a new transaction and see if the blob id is still valid.

=>

Using a java.sql.Blob instance from a result set yields a NullPointerException after commit, instead it should yield an error that the blob is not available after commit.

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Fixed

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]

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