I have a wild idea but maybe you can check with the vendor if it can be
done.
1) Create a table that will hold only the other fields.
2) Create a second table that will have the same PK and long raw field.
3) Create a view that will combine them by the PK.
4) Since I am not sure in a view with
Group,
I have just been given a project / database
where a vendor will implement a table
with a LONG RAW field in it.
Oracle manuals state clearly that this datatype
is outdated and should be replaced by BLOB,
I quoted the manuals to vendor-support, but they
will not move on this.
From the
The reason that vendors often use LONG RAW is that that datatype meets the ANSI SQL
standard, while BLOB doesn't. That way, they can use the same DDL against most SQL
databases. Sometimes you can modify the vendor's DDL before or during installation.
Sometimes you can re-create a table right
