Re: JDBC and CLOB retrieval question

Martin Gregorie wrote:
Peter Fourneau wrote:
if you work with a Clob:
I tried to avoid using Clob because that chews up memory if you're using large amounts of data and Clobs could be multi-megabytes on occasion.

The whole point of Clob is that it avoids reading the entire object
into memory.

Arne
.

Relevant Pages

  • Re: are arrays contiguous in memory?
    ... >> (and as a side benefit saves memory, is more intuitive, is less prone to ... > Arnaud has correctly pointed out that lookups with lists are of O ... > speeds don't change this. ... Indeed, for large amounts of data, it matters a lot. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: [linux-pm] Re: Hibernation considerations
    ... need to allocate large amounts of memory. ... Why should the error handler wake up? ...
    (Linux-Kernel)
  • Re: strdup()
    ... > amounts of memory, or random amounts, or imaginary amounts, or amounts ... memory allocated may depend on input to the program. ... A program that allocates exactly 42 fixed-size buffers during startup ... has deterministic memory usage. ...
    (comp.lang.c)
  • Re: checking if text has changed
    ... clob. ... if the sql didn't return any rows, then i know that somebody change the ... When the user tries the save the data, you read the record again and compare what's held in memory against what was just read. ...
    (comp.programming)
  • Re: PAT support
    ... > This would also be extremely useful on machines with large amounts ... > of memory, for write-back mappings. ... With large amounts but odd sized ... But for this it will need some more work - the MTRRs need to be fully ...
    (Linux-Kernel)