For example, some drivers may define their (SQL) BLOB types as JDBC LONGVARBINARY instead (which supports getBytes and getBinaryStream), but may then also define support for getBlob for cases where users assume "I use a SQL BLOB, so I should use getBlob". bridge implementation differences between different database systems). However, some drivers are more lenient, either for backwards compatibility with earlier versions of the driver, or for maximum portability (e.g. A is the Java representation of that locator object, providing an indirection to access the off-row data of the blob. BLOB data is generally stored off-row (the row only contains a pointer or id of the actual data), whereas BINARY (and VARBINARY) are usually stored inline. Whereas a SQL (and JDBC) BLOB is a type holding binary data of varying length (usually of unlimited length (or at least extremely large)) through a so-called locator object.
To be clear, JDBC type BINARY - usually - maps to/from the SQL type BINARY (Derby's equivalent is called CHAR FOR BIT DATA), which is a fixed-length byte string/array type.
See also the JDBC 4.3 specification, appendix B, specifically table B-3, which defines the default Java type for JDBC type BINARY as byte, and B-5, which only defines a mapping from a to JDBC type BLOB, and B-6 which only defines support for getBlob for columns of JDBC type BLOB. Using getBytes is always the appropriate method for this type ( getBinaryStream should also work). Using for JDBC type BINARY is wrong from a strict JDBC API interpretation, no matter which driver you use. | A | B | C | D | E | F | a | b | c | d | e | fĪn attempt was made to get a data value of type '' from a data value of type 'CHAR () FOR BIT DATA' (as implemented by DB2, Derby, H2, HSQLDB, Ingres, MySQL, SQLite): SQL Standard - SQL actually defines binary literals as such See A.H.'s answer for more details about Postgres' hex encoding Postgres - There is also hex encoding as of Postgres 9.0 INSERT INTO lob_table VALUES (hextoraw('01FF')) limitation of Oracle's VARCHAR types to hold only 4000 bytes! Oracle - As mentioned by a_horse_with_no_name, keep in mind the relatively low INSERT INTO lob_table VALUES (blob(X'01FF')) ĭerby, H2, HSQLDB, Ingres, MySQL, SQLite INSERT INTO lob_table VALUES (X'01FF') This is not needed for VARCHAR FOR BIT DATA types SQL Server, Sybase ASE, Sybase SQL Anywhere INSERT INTO lob_table VALUES (0x01FF) ĭB2 - Use a blob constructor. There probably isn't a JDBC escape syntax, so I searched around a bit and found and successfully tested the following: Inline BLOB / BINARY data types in SQL / JDBC
0 kommentar(er)
