Re: ERROR: relation . . . does not exist

From: Christophe <xof(at)thebuild(dot)com>
To: PGSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR: relation . . . does not exist
Date: 2008-08-30 17:40:44
Message-ID: 072373D9-35C5-454E-A18E-8E512D3136B5@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Aug 30, 2008, at 10:33 AM, Albretch Mueller wrote:
> well, yeah! I would totally agree with you, but since I doubt very
> much "COPY FROM CSV" is part of the SQL standard to beging with, why
> not spice it up a little more?

I'd guess that coming up with a general algorithm to guess the type
from a column of CSV text would satisfy no one, since we'd always
miss a particular case that is important to someone (are times local
or UTC? Should we assume integer or float? Varchar or text?), and the
option is a forest of switches that would be extremely complex and
error prone.

This sounds very much like an application-domain problem, best solved
in the application domain.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albretch Mueller 2008-08-30 20:42:39 Re: ERROR: relation . . . does not exist
Previous Message Martijn van Oosterhout 2008-08-30 17:39:15 Re: DUPS in tables columns ERROR: column ". . . " does not exist