The warning is erroneous.' same here, i keep getting this warning, but they definitely have where clauses.

My suggestion is that SQL Prompt should recognize the tables that have constraints such as these (CK with constant value on the PK column) and should not produce warnings for UPDATE-s without WHERE clauses on such tables. 'If the deletion is on a table join, I don't want to be told that I have no where clause. In Sql Server 2016 we can write a statement like below to drop a DataBase if exists. We could also disable the warning, but I fear that someday I will see such a warning that is actually useful (although this did not happen yet, in the last few months since I'm using this feature). We have to drop the database from the database prompt in PostgreSQL.

Of course, we could add a WHERE clause (such as 'WHERE DummyID=1') in all the UPDATE statements, but there are a lot of statements (and many configuration tables). SQL Prompt always produces warnings when we update such tables, because we did not write any WHERE condition. To ensure this, we always use some constraints, like these:ĭummyID tinyint CONSTRAINT DEFAULT (1),ĬONSTRAINT PRIMARY KEY (DummyID),ĬONSTRAINT CHECK (DummyID=1), We have several tables with various configuration settings, which will always have a single row.

Sql prompt where clause warning