From: | missive(at)frontiernet(dot)net (Lee Harr) |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Data in a field must be in capitals |
Date: | 2002-02-08 03:11:29 |
Message-ID: | a3vfl1$13oq$2@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> I am using PostgreSQL7.1.3.
>
> I need to ensure that a project code is all in capitals (upper case) when it
> is stored in the database.
>
> To do this, should I use a trigger on an insert with a stored procedure, or
> a check constraint?
>
> I was planning on automatically converting lower case to upper case, rather
> than rejecting an invalid entry.
>
I was reading some of the comments on the PostgreSQL release story
on Slashdot and someone mentioned using functions for all regular
access to the database. It is an interesting idea.
Basically, the only access you give to insert in to the table
would be through a function, and you make sure your function
uppercases that particular field. Of course if people have access
to performing raw inserts then you would probably want a
trigger to verify the integrity of inserted data.
From | Date | Subject | |
---|---|---|---|
Next Message | Darren Ferguson | 2002-02-08 04:40:54 | Re: Data in a field must be in capitals |
Previous Message | Command Prompt, Inc. | 2002-02-08 02:10:21 | S-ODBC in Final Testing |