If you define the columns with double quotes, then you generally need to use them when you refer to the column: insert into tester3 (“UN0”, “UN1”) values ( 1, ‘jishnu1′); I would suggest you remove the double quotes from the column names in the CREATE TABLE statement. You don’t need the double quotes if the … Read more
put table name into double quotes if you want postgres to preserve case for relation names. Quoting an identifier also makes it case-sensitive, whereas unquoted names are always folded to lower case. For example, the identifiers FOO, foo, and “foo” are considered the same by PostgreSQL, but “Foo” and “FOO” are different from these three … Read more
You accidentally created the column name with a trailing space and presumably phpPGadmin created the column name with double quotes around it: create table your_table ( “foo ” — … ) That would give you a column that looked like it was called foo everywhere but you’d have to double quote it and include the … Read more
Try to take it into double quotes – like “Continent” in the query: SELECT “Continent” FROM network.countries …
From what I’ve read, this error means that you’re not referencing the table name correctly. One common reason is that the table is defined with a mixed-case spelling, and you’re trying to query it with all lower-case. In other words, the following fails: CREATE TABLE “SF_Bands” ( … ); SELECT * FROM sf_bands; — ERROR! … Read more