I am creating an image gallery system, where there is an admin and
multiple users upload images. Each user is restricted to uploading 8
images. Currently, I have this hard coded into a trigger. I would
like it to use a table field instead... one that the admin can change
on the fly. I want to call this table Settings, but I want to create
insert 1 record, and then block all subsequent INSERT statements
(there's only going to be 1 setting) so that the Settings table will
only have 1 record in it for its entire lifetime. What's the best way
to do this?

I would create a table like this:

CREATE TABLE Settings (
DummyID tinyint DEFAULT (1) PRIMARY KEY CHECK (DummyID=1),
MaximumImages int NULL DEFAULT (8)
-- ... and other settings when needed
)

INSERT INTO Settings DEFAULT VALUES

Razvan

Thanks.

Razvan Socol wrote: