Re: op error no question, but no error warning - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: op error no question, but no error warning
Date
Msg-id 20030312064901.T52741-100000@megazone23.bigpanda.com
Whole thread Raw
In response to op error no question, but no error warning  (Theodore Petrosky <tedpet5@yahoo.com>)
List pgsql-bugs
On Wed, 12 Mar 2003, Theodore Petrosky wrote:

> This isn't all my problem...
>
> I was going through tutorials, and I typed in the
> example for inheritance. I had a typo that did not
> throw an error and I think it should.
>
> i created the tables from the cities, capitals example
> and then tried to insert.
>
> test-db=# insert into capitals (name, population,
> state) values ('Trenton', '543565, 'New Jersey');
>
> my typo is the extra single quote before the number. I
> received no error message, but of course there was no
> insert. I would have assumed that the trailing ';'
> would have terminated the insert and if there is an
> error, it should have said so.

That ; is inside a single quoted string, it's not an
end of statement character, it's taken as a literal ;.
The prompt should change to something like
test-db'# to let you know that you're inside a literal.

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: RI Bug In Inherited Table
Next
From: Josh Berkus
Date:
Subject: Re: Aliased SubSelect in HAVING clause bug -- in progress?