Thread

  1. data larger than 8k

    Danny Rice <dwrice@indiana.edu> — 1998-07-16T16:40:18Z

    If a table element can only handle up to 8k of data what do you do if
    you need to insert larger data?
    
    -- 
    Danny Rice
    
    
  2. RE: [SQL] data larger than 8k

    Rostislav Matl <xmatl@informatics.muni.cz> — 1998-07-16T16:58:56Z

    On 16-Jul-98 Danny Rice wrote:
    > 
    > If a table element can only handle up to 8k of data what do you do if
    > you need to insert larger data?
    > 
    > -- 
    > Danny Rice
    
    Use large_objects - it's in man pages.
    
    +-----------------------------------------------------------------------------+
    |  ROSTISLAV MATL, student of Masaryk University - Faculty of Informatics     |
    |  e-mail: xmatl@fi.muni.cz      WWW: http://www.fi.muni.cz/~xmatl/index.html | 
    +-----------------------------------------------------------------------------+
    
    
  3. RE: [SQL] data larger than 8k

    Danny Rice <dwrice@indiana.edu> — 1998-07-18T17:43:00Z

     > 
     > On 16-Jul-98 Danny Rice wrote:
     > > 
     > > If a table element can only handle up to 8k of data what do you do if
     > > you need to insert larger data?
     > 
     > Rostislav Matl writes:
     > Use large_objects - it's in man pages.
    
    Thanks,
    
    I noticed that
    
    create table test (name text, filename oid);
    insert into test values ( 'a file', lo_import('/tmp/afile') );
    
    will create database files named as xinv(BigInteger) and
    xinx(BigInteger).
    
    When I do
    
    delete from test;
    or
    drop table test;
    
    These xin files stay around.  Is there a way to have these cleaned up
    on delete and drop?
    
    -- 
    Danny Rice
    
    
  4. RE: [SQL] data larger than 8k

    Peter Mount <peter@retep.org.uk> — 1998-07-19T09:40:51Z

    On Sat, 18 Jul 1998, Danny Rice wrote:
    
    > create table test (name text, filename oid);
    > insert into test values ( 'a file', lo_import('/tmp/afile') );
    > 
    > will create database files named as xinv(BigInteger) and
    > xinx(BigInteger).
    > 
    > When I do
    > 
    > delete from test;
    > or
    > drop table test;
    > 
    > These xin files stay around.  Is there a way to have these cleaned up
    > on delete and drop?
    
    This is a work in progress. In the developer source, take a look in
    contrib/lo which defines a new type 'lo' which handles large object
    orphaning. It can handle 'delete from test' but not 'drop table test'.
    
    -- 
    Peter T Mount peter@retep.org.uk or petermount@earthling.net
    Main Homepage: http://www.retep.org.uk
    ************ Someday I may rebuild this signature completely ;-) ************
    Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk