Skip site navigation (1) Skip section navigation (2)

Re: libpqxx Large Objects

From: "Key88 SF" <key88sf(at)hotmail(dot)com>
To: jtv(at)xs4all(dot)nl
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: libpqxx Large Objects
Date: 2003-01-09 18:04:14
Message-ID: F146bP4UzqYx2maKL6e0002c243@hotmail.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
I just tried a simple test program, and I'm getting a runtime exception 
thrown from the internal call to PQexec(). I'm going to try and find out 
what's wrong, but was wondering if anyone knows why this is happening before 
I start digging through libpq now.

My setup is:
PostgreSQL running on Linux box.
Test app with libpqxx running on Win32. Connects via TCP/IP to the database 
over my LAN.



>From: "Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl>
>To: Key88 SF <key88sf(at)hotmail(dot)com>
>CC: pgsql-interfaces(at)postgresql(dot)org
>Subject: Re: [INTERFACES] libpqxx Large Objects
>Date: Thu, 9 Jan 2003 03:34:43 +0100
>MIME-Version: 1.0
>Received: from mc4-f38.law16.hotmail.com ([65.54.237.173]) by 
>mc4-s12.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 8 Jan 
>2003 18:34:59 -0800
>Received: from relay2.pgsql.com ([64.49.215.143]) by 
>mc4-f38.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 8 Jan 
>2003 18:34:59 -0800
>Received: from postgresql.org (postgresql.org [64.49.215.8])by 
>relay2.pgsql.com (Postfix) with ESMTPid B6D40EE0A9D; Wed,  8 Jan 2003 
>21:34:51 -0500 (EST)
>Received: from localhost (postgresql.org [64.49.215.8])by postgresql.org 
>(Postfix) with ESMTP id A492E4758C9for <pgsql-interfaces(at)postgresql(dot)org>; 
>Wed,  8 Jan 2003 21:34:42 -0500 (EST)
>Received: from mxzilla2.xs4all.nl (mxzilla2.xs4all.nl [194.109.6.50])by 
>postgresql.org (Postfix) with ESMTP id D5D52474E42for 
><pgsql-interfaces(at)postgresql(dot)org>; Wed,  8 Jan 2003 21:34:41 -0500 (EST)
>Received: from xs1.xs4all.nl (xs1.xs4all.nl [194.109.3.11])by 
>mxzilla2.xs4all.nl (8.12.3/8.12.3) with ESMTP id h092YhQV002899;Thu, 9 Jan 
>2003 03:34:43 +0100 (CET)
>Received: (from jtv(at)localhost)by xs1.xs4all.nl (8.11.6/8.11.6) id 
>h092Yhl01524;Thu, 9 Jan 2003 03:34:43 +0100 (CET)(envelope-from jtv)
>Message-ID: <20030109023443(dot)GC80851(at)xs4all(dot)nl>
>Mail-Followup-To: Key88 SF 
><key88sf(at)hotmail(dot)com>,pgsql-interfaces(at)postgresql(dot)org
>References: <F181CJLgRkQ9ZPWv1QJ000270f6(at)hotmail(dot)com>
>In-Reply-To: <F181CJLgRkQ9ZPWv1QJ000270f6(at)hotmail(dot)com>
>User-Agent: Mutt/1.4i
>X-Virus-Scanned: by AMaViS new-20020517
>Precedence: bulk
>Sender: pgsql-interfaces-owner(at)postgresql(dot)org
>Return-Path: pgsql-interfaces-owner+M3551(at)postgresql(dot)org
>X-OriginalArrivalTime: 09 Jan 2003 02:34:59.0675 (UTC) 
>FILETIME=[B4830AB0:01C2B787]
>
>On Thu, Jan 09, 2003 at 12:23:18AM +0000, Key88 SF wrote:
> >
> > Really? Where do you see that? I'm looking at the libpq - C library
> > documentation, section 2, describing large objects. I don't see any
> > mention of the interface being deprecated.
>
>It doesn't seem to be documented there, no.  I've no time to dig it
>up now (I'll be on a holiday for the coming week) so you may just want
>to search the site.  Or just see if postgres will handle the kind of
>object size you need as native table data.
>
>BTW, yes, libpq++ had notional large-object support--but that was
>never actually fully functional, from what I hear.
>
>Jeroen
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)


_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail


Responses

pgsql-interfaces by date

Next:From: Peter EisentrautDate: 2003-01-09 21:49:53
Subject: Re: Recasting types
Previous:From: Gerhard HintermayerDate: 2003-01-09 11:06:33
Subject: Re: still memory leaks with libpgtcl

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group