home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!oracle!unrepliable!bounce
- Newsgroups: comp.databases.oracle
- From: rhari@us.oracle.com
- Subject: Re: Eating it RAW
- Message-ID: <1992Nov10.151345.1@us.oracle.com>
- Lines: 30
- Sender: usenet@oracle.us.oracle.com (Oracle News Poster)
- Nntp-Posting-Host: kervms.us.oracle.com
- Organization: Oracle Corporation, USA
- References: <BxGJw1.Kr1@well.sf.ca.us>
- Distribution: usa
- Date: Tue, 10 Nov 1992 23:13:45 GMT
- X-Disclaimer: This message was written by an unauthenticated user
- at Oracle Corporation. The opinions expressed are those
- of the user and not necessarily those of Oracle.
-
- In article <BxGJw1.Kr1@well.sf.ca.us>, mharper@well.sf.ca.us (Michael J. Harper) writes:
- > I am trying to store data into a LONG RAW column, and I am running into
- > some difficulty.
- >
- > The data I would like to store happens to be TIFF data. Consequently, it
- > is a minimum of 4K or so in size. When I tried using HEXTORAW with an 8K
- > string, I was told that my string was too long. So, I divided the string
- > into a bunch of 254-character strings all concatenated. No parse error,
- > but only the first 256 characters were stored anyway. This gives me only
- > 128 bytes of raw data, which isn't quite enough.
- >
- > So, is there another way to issue an INSERT that will allow me to store up to
- > the full length of my LONG RAW?
- >
- > Also, I noticed that when I fetch this column, the first byte seems to be
- > the row number in the query. Does anyone know what this byte really means
- > and what it's doing at the beginning of my raw data?
- >
- > Thanks.
- > --
- > Michael J. Harper
- > mharper@well.sf.ca.us
- --
- I presume you are using version 6 of ORACLE.
-
- The best way to handle raw data is thru OCI or Pro* languages.
-
-
- Radhakrishna Hari
- rhari@us.oracle.com
-