Re: sequence in schema -- broken default - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: sequence in schema -- broken default
Date
Msg-id 40118951.4030706@commandprompt.com
Whole thread Raw
In response to Re: sequence in schema -- broken default  (Martín Marqués<martin@bugs.unl.edu.ar>)
List 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@commandprompt.com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL


pgsql-general by date:

Previous
From: vhikida@inreach.com
Date:
Subject: Re: If table A value IS NULL then table B
Next
From: Tom Lane
Date:
Subject: Re: Article in German iX magazine