Re: sequence in schema -- broken default
От | Joshua D. Drake |
---|---|
Тема | Re: sequence in schema -- broken default |
Дата | |
Msg-id | 40118951.4030706@commandprompt.com обсуждение исходный текст |
Ответ на | Re: sequence in schema -- broken default (Martín Marqués<martin@bugs.unl.edu.ar>) |
Список | 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 по дате отправления: