From: | dmp <danap(at)ttc-cmc(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL Array Use |
Date: | 2008-03-04 02:07:47 |
Message-ID: | 47CCAEF2.6080808@ttc-cmc.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I was slightly confused. I'm really trying to identify what type
of support the project should provide to array types. Just from
the input so far, it looks like more needs to be done. If 100's to
1000's of elements are in an array type, the application is going
to have some problems. Presently it will adequately handle less
then 10 or 20 elements in multi-dimensional arrays, without
much problem with adding, editing, & viewing, but 100s to 1000s
of elements need a more robust & easy method to view and edit
elements. The data type of the array is not a real problem, except
bytea and some of the geometry types which have some specific
input form requirements. Text might be a problem if the byte
size is large.
danap.
On Mar 3, 2008, at 2:05 PM, Josh Trutwin wrote:
> On Mon, 3 Mar 2008 20:48:55 +0100
> Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> wrote:
>
>> On Mon, Mar 03, 2008 at 01:22:17PM -0600, Erik Jones wrote:
>>
>>> Where are you getting this information.
>>
>> IMO the OP wanted to know how people *use* arrays, not how
>> one *can* use arrays.
>
>
> That was my thought, sort of a poll. Hopefully OP isn't confused
> now. :)
Ah, I sure was then :)
Erik Jones
From | Date | Subject | |
---|---|---|---|
Next Message | Jorge Godoy | 2008-03-04 02:41:50 | Re: Connect to postgres from a dynamic IP |
Previous Message | Tom Lane | 2008-03-03 23:26:57 | Re: partitioning using dblink |