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

Re: pgAdmin3 feature freeze?

From: "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>
To: "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>
Cc: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>,<pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: pgAdmin3 feature freeze?
Date: 2003-06-25 00:47:31
Message-ID: 03e501c33ab3$5c4f1730$1f324d80@w2k (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
Hi Andreas.

From: "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>
> Hiroshi Saito wrote:
> >Hi Andreas.
> >
> >I am sorry that my response is dull...
> >
> >I thought how pgadmin3 should handle LargeObject.
> >There is the following three approach with pgsql-7.3 as the way of
> >it.
> >
> >
> Hiroshi,
> pgAdmin3 doesn't handle blobs at the moment, because it doesn't work
> with data a lot. If a selected column contains lo or bytea, the string
> output of libpq is shown. This might not be pretty looking, but
> interpretation of a blob is up to an application. I don't see a way to
> handle this in a meaningful way for the tools we have in pgAdmin3 at the
> moment.
> This might change if we support some dump/restore or load functionality,
> but this is a feature of forthcoming versions.

It was understood.
With the material which I enjoy.


In response to

pgadmin-hackers by date

Next:From: Hiroshi SaitoDate: 2003-06-25 01:07:54
Subject: patch of wxstring, ..
Previous:From: Adam H.PendletonDate: 2003-06-24 23:03:30
Subject: frmQueryBuilder.patch

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