I was wrong. A code change is necessary to read progtxt when it is defined as BLOB.
As far as I can tell, Oracle implemented progtxt as a BLOB of bytes. It is easily read into a byte array.
Previously progtxt was implemented as LONG RAW. I believe it is because of the limited functionality the Oracle database has with data type LONG RAW that although it's the same data as stored in BLOB it is necessary to read it into a String, convert it to a char array and convert that to a byte array.
The code for MySQL assumes the BLOB data is binary.
Method stagePeopleCode(Connection, String) from decodePC.java for reading pspcmprog when progtxt is of data type BLOB has been posted. decodePC.java will eventually be changed to read the Oracle catalog to determine progtxt's datatype and work with both LONG RAW and BLOB.
Code change necessary to read Oracle BLOB pspcmprog.progtxt
Hi,
I was wrong. A code change is necessary to read progtxt when it is defined as BLOB.
As far as I can tell, Oracle implemented progtxt as a BLOB of bytes. It is easily read into a byte array.
Previously progtxt was implemented as LONG RAW. I believe it is because of the limited functionality the Oracle database has with data type LONG RAW that although it's the same data as stored in BLOB it is necessary to read it into a String, convert it to a char array and convert that to a byte array.
The code for MySQL assumes the BLOB data is binary.
Method stagePeopleCode(Connection, String) from decodePC.java for reading pspcmprog when progtxt is of data type BLOB has been posted. decodePC.java will eventually be changed to read the Oracle catalog to determine progtxt's datatype and work with both LONG RAW and BLOB.