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

Re: ERROR: relation . . . does not exist

From: "Albretch Mueller" <lbrtchx(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: relation . . . does not exist
Date: 2008-08-30 13:26:44
Message-ID: 9ef66fac0808300626x16f3e9fds6d9d5996470faf9d@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
> I think you're confusing postgresql with a spreadsheet program.
~
 I wonder what makes you think so
~
> There are client programs which will do this for you, perhaps you wan one of those?
~
 Well, then obviously there is the need for it and you were not
successful enough at convincing these developers that they were
"confusing postgresql with a spreadsheet program"
~
> PostgreSQL has 60+ types and many look like eachother. How do you propose to differentiate?
~
 Data Types are basically about value ranges (how many bits do you
need to hold the value) and formatting. IMHO, finding an optimal
[im|ex]port reasoning among 60+ types should not be that much of a big
deal. In fact as a data analyst I have exported and imported CSV data
a whole lot and in many occasions it required some extra custom
coding. I may as well consolidate my code as a whole jcsvport library
in java and start an OS project when I find the time to so
~
 lbrtchx

In response to

Responses

pgsql-general by date

Next:From: Stefan KaltenbrunnerDate: 2008-08-30 14:24:52
Subject: Re: DUPS in tables columns ERROR: column ". . . " does not exist
Previous:From: Albretch MuellerDate: 2008-08-30 13:05:50
Subject: Re: DUPS in tables columns ERROR: column ". . . " does not exist

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