| Summary: | Incorrect handling of PostgreSQL's BLOB | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Michal Piotrowski <mpiotrowski> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P2 | CC: | aaron.lisman, igor.paunov, lista, martin.grebac, nenad, tom.ware | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | postgresql | ||||||
| Attachments: |
|
||||||
|
Description
Michal Piotrowski
Created attachment 189206 [details]
Code for recognizing blob's in PostgreSQL
This is a very simple patch which correctly recognizes BLOBs in PostgreSQL.
I couldn't correctly test it in JavaSE, because EclipseLink works in JDBC autoCommit mode, and BLOBs in PostgreSQL can't be read in autoCommit mode. :(
I have tried:
entityManager.getTransaction().begin();
before executing:
entityManager.find()
but drivers autoCommit mode wasn't disabled!
I'm afraid that I don't know EclipseLink code well enough to propose fully working patch.
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |