> > How hard would it be to support this (standard) behaviour for
> > inserting/update binary data via scripts?
> >
> > INSERT INTO myblobtable (0xAE01498921);
>
> What does this operation mean?
> Since I don't see the VALUES keyword, I assume that such binary

information

> represents the whole record. Can you clarify, please?

Typo on my part...

CREATE TABLE mytable
( I Integer,
B BLOB);

COMMIT;

INSERT INTO mytable (I, B) VALUES (1, 0xAE01498921);

INSERT INTO mytable (I, B) VALUES (1, 0x000060000060000080);

etc...

This would insert a blob with each byte written as a hex value. The
"0x......" would be the blob.

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com