I have one table in which I would like only one entry. So if someone is trying to insert another row it shouldn't be allowed, only after someone deleted the previously existing row.
How do I set a rule for a table like this?
To return only the first row that matches your SELECT query, you need to add the LIMIT clause to your SELECT statement. The LIMIT clause is used to control the number of rows returned by your query. When you add LIMIT 1 to the SELECT statement, then only one row will be returned.
While the table name is selected type CTRL + 3 and you will notice that the query will run and will return a single row as a resultset. Now developer just has to select the table name and click on CTRL + 3 or your preferred shortcut key and you will be able to see a single row from your table.
To select rows using selection symbols for character or graphic data, use the LIKE keyword in a WHERE clause, and the underscore and percent sign as selection symbols. You can create multiple row conditions, and use the AND, OR, or IN keywords to connect the conditions.
A UNIQUE
constraint allows multiple rows with NULL
values, because two NULL
values are never considered to be the same.
Similar considerations apply to CHECK
constraints. They allow the expression to be TRUE
or NULL
(just not FALSE
). Again, NULL
values get past the check.
To rule that out, the column must be defined NOT NULL
. Or make it the PRIMARY KEY
since PK columns are defined NOT NULL
automatically. Details:
Also, just use boolean
:
CREATE TABLE public.onerow ( onerow_id bool PRIMARY KEY DEFAULT TRUE , data text , CONSTRAINT onerow_uni CHECK (onerow_id) );
The CHECK
constraint can be that simple for a boolean
column. Only TRUE
is allowed.
You may want to REVOKE
(or not GRANT
) the DELETE
and TRUNCATE
privileges from public
(and all other roles) to prevent the single row from ever being deleted. Like:
REVOKE DELETE, TRUNCATE ON public.onerow FROM public;
Add a new column to the table, then add a check constraint and a uniqueness constraint on this column. For example:
CREATE TABLE logging ( LogId integer UNIQUE default(1), MyData text, OtherStuff numeric, Constraint CHK_Logging_singlerow CHECK (LogId = 1) );
Now you can only ever have one row with a LogId = 1. If you try to add a new row it will either break the uniqueness or check constraint.
(I might have messed up the syntax, but it gives you an idea?)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With