Formating of SQL value for BLOB types (as hex vs ascii-bytes)

∟Reference Citations in 2010

∟Formating of SQL value for BLOB types (as hex vs ascii-bytes)

'Inserting BLOB Values with SQL INSERT Statements' tutorial was cited in a message in the H2 Database Google group posted in 2010.

The Inserting BLOB Values with SQL INSERT Statements tutorial was cited in a message in the H2 Database Google group posted in 2010.

Subject: Formating of SQL value for BLOB types (as hex vs ascii-bytes)
Date: Mar 1, 2010
Author:  kensystem
Source: http://groups.google.com/group/h2-database/browse_thread
   /thread/a7abae217ab99ad9/9efc6ed35b93c2eb?show_docid=9efc6ed35b93c2eb

...

Since I no longer have access to sql specs, here are some links that
hopefully describe the two different modes, explicit hex (hinted with
'x') encoding, vs (char)byte:

This shows PG's old encoding ( it is (char)byte, but adds-in the
extraneous 92 which I don think is needed in newer PG, and also 0
which is needed just for the wire protocol as I understand):
http://www.sql.org/sql-database/postgresql/manual/datatype-binary.html

https://www.herongyang.com/jdbc/Oracle-BLOB-SQL-INSERT.html (it does
not say what would happen for each server if using the (char)byte
method (escaping only 0x39) Oracle, is different and unique becasue
it defaults to hex mode (Oracle is)... H2 is mimicking this but I
don't believe it should.

...