Albretch Mueller wrote:
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.
That is exactly wrong, at least in the PostgreSQL approach to the ty
Albretch Mueller wrote:
Varchar or text?
~
Is the length of the data read in always less than 255 bytes ( or
characters?)? ...
It may be more limited than that by application-domain-specific constraints -
e.g., a license plate might be statutorily limited to eight characters.
It might be
You have made clear to me why my attempt for a RFE for COPY FROM CVS
has found some technical resistance/disagreement, but I still think my
idea even if not so popular for concrete and cultural reasons makes at
least sense to some people
It's a perfectly reasonable problem to want to solve; th
> ... are times local or UTC
~
this is a rather semantic, not a syntactic issue that some code could
NOT decide based on the data it reads
~
> Should we assume integer or float?
~
is a dot anywhere in the data you read in for that particular column? ...
~
> Varchar or text?
~
Is the length of th
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
fr
On Saturday 30 August 2008 9:42:19 am Adrian Klaver wrote:
> On Saturday 30 August 2008 5:23:25 am Albretch Mueller wrote:
> > On Thu, Aug 28, 2008 at 7:50 PM, Adrian Klaver <[EMAIL PROTECTED]>
wrote:
> > > Define easily.
> >
> > ~
> > OK, let me try to outline the approach I would go for:
> > ~
> spreadsheet programs (generally; I'm sure there are exceptions) don't have
> the notion of a schema; each cell can hold its own particular type.
~
Oh, now I see what Martin meant!
~
> that's not a traditional part of a database engine.
~
well, yeah! I would totally agree with you, but since I
On Aug 30, 2008, at 9:19 AM, Christophe wrote:
On Aug 30, 2008, at 6:26 AM, Albretch Mueller wrote:
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"
The behavior y
On Saturday 30 August 2008 5:23:25 am Albretch Mueller wrote:
> On Thu, Aug 28, 2008 at 7:50 PM, Adrian Klaver <[EMAIL PROTECTED]> wrote:
> > Define easily.
>
> ~
> OK, let me try to outline the approach I would go for:
> ~
> I think "COPY FROM CSV" should have three options, namely:
> ~
> 1) th
On Aug 30, 2008, at 6:26 AM, Albretch Mueller wrote:
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"
The behavior you are looking for is typical of a spreadsheet, b
> 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 de
On Sat, Aug 30, 2008 at 08:23:25AM -0400, Albretch Mueller wrote:
> OK, let me try to outline the approach I would go for:
> ~
> I think "COPY FROM CSV" should have three options, namely:
I think you're confusing postgresql with a spreadsheet program. A
database is designed to take care of your
On Thu, Aug 28, 2008 at 7:50 PM, Adrian Klaver <[EMAIL PROTECTED]> wrote:
> Define easily.
~
OK, let me try to outline the approach I would go for:
~
I think "COPY FROM CSV" should have three options, namely:
~
1) the way we have used it in which you create the table first
~
2) another way in w
On Thursday 28 August 2008 3:14:01 pm Albretch Mueller wrote:
> On Thu, Aug 28, 2008 at 5:40 PM, Raymond O'Donnell <[EMAIL PROTECTED]> wrote:
> > You have to create the table first before you can COPY into it.
>
> ~
> Well, based on how the statement reads I made the wrong assumption of
> thinking
On Thu, Aug 28, 2008 at 5:40 PM, Raymond O'Donnell <[EMAIL PROTECTED]> wrote:
> You have to create the table first before you can COPY into it.
~
Well, based on how the statement reads I made the wrong assumption of
thinking that PG would be smart enough to make ends-meat with the
data that it ge
On 28/08/2008 22:29, Albretch Mueller wrote:
> jpk=# COPY j2sdk_1_4_2_18_binfls_md5sum FROM
> '/media/hda3/prjx/JPack/REF/LANDMARKS/PROFILES/20080828104627_j2sdk-1_4_2_18-linux-i586.binfls.md5sum.txt'
> CSV HEADER;
> ERROR: relation "j2sdk_1_4_2_18_binfls_md5sum" does not exist
> ~
> What is goi
16 matches
Mail list logo
