| Computers Forum Index » Computer - Databases - Oracle (Server) » CLOB... |
|
Page 1 of 1 |
|
| Author |
Message |
| The Magnet... |
 Posted: Wed Nov 04, 2009 10:23 pm |
|
|
|
Guest
|
This may be a dumb question, but why can't Oracle read anything
greater than 32767?? Even CLOB's? You really have to loop and do
some crappy stuff?? |
|
|
| Back to top |
|
|
|
| joel garry... |
| Posted: Thu Nov 05, 2009 12:33 am |
|
|
|
Guest
|
On Nov 4, 2:23 pm, The Magnet <a... at (no spam) unsu.com> wrote:
Quote: This may be a dumb question, but why can't Oracle read anything
greater than 32767?? Even CLOB's? You really have to loop and do
some crappy stuff??
Not a dumb question at all. I think the answer is simply the string
length limit of PL/SQL.
In general with CLOB's, you have to deal with the physical realities
of limits in the db. It's harder to just make everything logical like
you theoretically should be able to with relational databases. So
physical limits are worked around by hiding in packages, or hiding the
realities in other languages.
jg
--
at (no spam) home.com is bogus.
http://www.cracked.com/photoshop_90_the-world-tomorrow-if-internet-disappeared-today_p19 |
|
|
| Back to top |
|
|
|
| Malcolm Dew-Jones... |
| Posted: Thu Nov 05, 2009 5:11 am |
|
|
|
Guest
|
The Magnet (art at (no spam) unsu.com) wrote:
: This may be a dumb question, but why can't Oracle read anything
: greater than 32767?? Even CLOB's? You really have to loop and do
: some crappy stuff??
What are you trying to do? I often use perl + DBI, and doing simple
inserts and selects of clobs (from/into bind variables mapped to perl
varables) requires no special handling, though you may need to set
LongReadLen ahead of time. |
|
|
| Back to top |
|
|
|
| Mark D Powell... |
| Posted: Thu Nov 05, 2009 4:01 pm |
|
|
|
Guest
|
On Nov 4, 5:23 pm, The Magnet <a... at (no spam) unsu.com> wrote:
Quote: This may be a dumb question, but why can't Oracle read anything
greater than 32767?? Even CLOB's? You really have to loop and do
some crappy stuff??
How are you trying to read the LOB? The sqlldr utility can read LOB's
over 32K. Now the utl_file utility used to have a 32K record size
limit in it. Are you using it?
What full version of Oracle? Oracle capabilities for dealing with LOB
data has evolved over the releases since 8.0 introdduced the data
type.
HTH -- Mark D Powell -- |
|
|
| Back to top |
|
|
|
| Mladen Gogala... |
| Posted: Thu Nov 05, 2009 6:03 pm |
|
|
|
Guest
|
On Wed, 04 Nov 2009 14:23:22 -0800, The Magnet wrote:
Quote: This may be a dumb question, but why can't Oracle read anything greater
than 32767?? Even CLOB's? You really have to loop and do some crappy
stuff??
The answer is that it can read. I used DBMS_LOB.READ to read the entire
1MB and that was in version 9i. The problem is that I was using C
language. What are you using?
--
http://mgogala.freehostia.com |
|
|
| Back to top |
|
|
|
| Mladen Gogala... |
| Posted: Thu Nov 05, 2009 6:21 pm |
|
|
|
Guest
|
On Wed, 04 Nov 2009 14:23:22 -0800, The Magnet wrote:
Quote: This may be a dumb question, but why can't Oracle read anything greater
than 32767?? Even CLOB's? You really have to loop and do some crappy
stuff??
The answer is that it can read. I used DBMS_LOB.READ to read the entire
1MB and that was in version 9i. The problem is that I was using C
language. What are you using?
--
http://mgogala.freehostia.com |
|
|
| Back to top |
|
|
|
| The Magnet... |
| Posted: Thu Nov 05, 2009 6:44 pm |
|
|
|
Guest
|
On Nov 5, 10:01 am, Mark D Powell <Mark.Powe... at (no spam) hp.com> wrote:
Quote: On Nov 4, 5:23 pm, The Magnet <a... at (no spam) unsu.com> wrote:
This may be a dumb question, but why can't Oracle read anything
greater than 32767?? EvenCLOB's? You really have to loop and do
some crappy stuff??
How are you trying to read the LOB? The sqlldr utility can read LOB's
over 32K. Now the utl_file utility used to have a 32K record size
limit in it. Are you using it?
What full version of Oracle? Oracle capabilities for dealing with LOB
data has evolved over the releases since 8.0 introdduced the data
type.
HTH -- Mark D Powell --
We are using PHP to perform the actual call to the DB. My solution
was to return 2 variables, breaking the CLOB up and having PHP receive
2 output values.
Still, a dumb limitation. You'd think by this point Oracle would have
fixed that. |
|
|
| Back to top |
|
|
|
| Mladen Gogala... |
| Posted: Thu Nov 05, 2009 9:08 pm |
|
|
|
Guest
|
On Thu, 05 Nov 2009 10:44:55 -0800, The Magnet wrote:
Quote: On Nov 5, 10:01Â am, Mark D Powell <Mark.Powe... at (no spam) hp.com> wrote:
On Nov 4, 5:23Â pm, The Magnet <a... at (no spam) unsu.com> wrote:
This may be a dumb question, but why can't Oracle read anything
greater than 32767?? Â EvenCLOB's? Â You really have to loop and do
some crappy stuff??
How are you trying to read the LOB? Â The sqlldr utility can read LOB's
over 32K. Â Now the utl_file utility used to have a 32K record size
limit in it. Â Are you using it?
What full version of Oracle? Â Oracle capabilities for dealing with LOB
data has evolved over the releases since 8.0 introdduced the data type.
HTH -- Mark D Powell --
We are using PHP to perform the actual call to the DB. My solution was
to return 2 variables, breaking the CLOB up and having PHP receive 2
output values.
Still, a dumb limitation. You'd think by this point Oracle would have
fixed that.
Have you tried posting the code on the OTN PHP forum? Chris Jones and some
other guys might be able to help you out.
--
http://mgogala.freehostia.com |
|
|
| Back to top |
|
|
|
| Mladen Gogala... |
| Posted: Thu Nov 05, 2009 9:09 pm |
|
|
|
Guest
|
On Thu, 05 Nov 2009 10:44:55 -0800, The Magnet wrote:
Quote: On Nov 5, 10:01Â am, Mark D Powell <Mark.Powe... at (no spam) hp.com> wrote:
On Nov 4, 5:23Â pm, The Magnet <a... at (no spam) unsu.com> wrote:
This may be a dumb question, but why can't Oracle read anything
greater than 32767?? Â EvenCLOB's? Â You really have to loop and do
some crappy stuff??
How are you trying to read the LOB? Â The sqlldr utility can read LOB's
over 32K. Â Now the utl_file utility used to have a 32K record size
limit in it. Â Are you using it?
What full version of Oracle? Â Oracle capabilities for dealing with LOB
data has evolved over the releases since 8.0 introdduced the data type.
HTH -- Mark D Powell --
We are using PHP to perform the actual call to the DB. My solution was
to return 2 variables, breaking the CLOB up and having PHP receive 2
output values.
Still, a dumb limitation. You'd think by this point Oracle would have
fixed that.
Have you tried posting the code on the OTN PHP forum? Chris Jones and some
other guys might be able to help you out.
--
http://mgogala.freehostia.com |
|
|
| Back to top |
|
|
|
| Malcolm Dew-Jones... |
| Posted: Thu Nov 05, 2009 11:43 pm |
|
|
|
Guest
|
The Magnet (art at (no spam) unsu.com) wrote:
: On Nov 5, 10:01=A0am, Mark D Powell <Mark.Powe... at (no spam) hp.com> wrote:
: > On Nov 4, 5:23=A0pm, The Magnet <a... at (no spam) unsu.com> wrote:
: >
: > > This may be a dumb question, but why can't Oracle read anything
: > > greater than 32767?? =A0 EvenCLOB's? =A0You really have to loop and do
: > > some crappy stuff??
: >
: > How are you trying to read the LOB? =A0The sqlldr utility can read LOB's
: > over 32K. =A0Now the utl_file utility used to have a 32K record size
: > limit in it. =A0Are you using it?
: >
: > What full version of Oracle? =A0Oracle capabilities for dealing with LOB
: > data has evolved over the releases since 8.0 introdduced the data
: > type.
: >
: > HTH -- Mark D Powell --
: We are using PHP to perform the actual call to the DB. My solution
: was to return 2 variables, breaking the CLOB up and having PHP receive
: 2 output values.
: Still, a dumb limitation. You'd think by this point Oracle would have
: fixed that.
First ask yourself what would happen to your php script if you read the
entire clob into a single variable - and the clob was (for example) 4
gigabytes in size. What portion of the software should handle that?
Should the Oracle networking return that as a single data item to the
application's oracle interface? Should the interface handle that so your
application doesn't see it? Should your application handle it itself?
I think it is obvious that the oracle networking should not return that as
a single item because then virtually no application or interface could
ever be sure of being able to handle clob data. That leaves the interface
or the application. As I mentioned earlier, I often use perl because the
DBI interface handles that issue so my applicaiton doesn't have to. From
other posts, it sounds like various other interfaces also handle the
issue.
As for php, my reading of the php documentation of OCI-Lob->load says it
can read any size up to "memory_limit", which appears to be set in
php.ini, though it is also limited by the compile time options of your php
executable. So perhaps the issue is the setup of the php you are using.
$0.10 |
|
|
| Back to top |
|
|
|
| Thomas Kellerer... |
| Posted: Fri Nov 06, 2009 12:40 am |
|
|
|
Guest
|
The Magnet wrote on 04.11.2009 23:23:
Quote: This may be a dumb question, but why can't Oracle read anything
greater than 32767?? Even CLOB's? You really have to loop and do
some crappy stuff??
I have no problem reading large CLOBs using JDBC....
Thomas |
|
|
| Back to top |
|
|
|
| Mark D Powell... |
| Posted: Fri Nov 06, 2009 3:00 pm |
|
|
|
Guest
|
On Nov 5, 1:44 pm, The Magnet <a... at (no spam) unsu.com> wrote:
Quote: On Nov 5, 10:01 am, Mark D Powell <Mark.Powe... at (no spam) hp.com> wrote:
On Nov 4, 5:23 pm, The Magnet <a... at (no spam) unsu.com> wrote:
This may be a dumb question, but why can't Oracle read anything
greater than 32767?? EvenCLOB's? You really have to loop and do
some crappy stuff??
How are you trying to read the LOB? The sqlldr utility can read LOB's
over 32K. Now the utl_file utility used to have a 32K record size
limit in it. Are you using it?
What full version of Oracle? Oracle capabilities for dealing with LOB
data has evolved over the releases since 8.0 introdduced the data
type.
HTH -- Mark D Powell --
We are using PHP to perform the actual call to the DB. My solution
was to return 2 variables, breaking the CLOB up and having PHP receive
2 output values.
Still, a dumb limitation. You'd think by this point Oracle would have
fixed that.
I do not think it is an Oracle limitation. Other tools as posted can
retrieve the entire lob at once, or at least larger LOB chunks. I
think researching the other suggestions and referring to whatever PHP
to Oracle documentation you can find is the next step.
HTH -- Mark D Powell -- |
|
|
| Back to top |
|
|
|
|
