Re: sequence in schema -- broken default

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Martín Marqués <martin(at)bugs(dot)unl(dot)edu(dot)ar>
Cc: Lee Harr <missive(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: sequence in schema -- broken default
Date: 2004-01-23 20:51:29
Message-ID: 40118951.4030706@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


>>>
>>>
>>Actually if you think about it, it makes sense. At least from the
>>example you provide.
>>insert into x values(5) is a integer insertion, and it just inserts into
>>the first column but
>>the second example insert into x values() specifies a blank value. A
>>blank is a string
>>(versus a NULL which is nothing) and the parser barfs on it with an
>>integer. Although
>>you will get a different error, insert into x values ('') will also fail.
>>
>>
>
>I feel as if the error message is saying that there's an error near ")" because
>there is a missing value (no value al all), not because he entered a string.
>
>
>
That is actually what I meant.

J

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-01-23 20:59:33 Re: Article in German iX magazine
Previous Message vhikida 2004-01-23 20:45:39 Re: If table A value IS NULL then table B