From: | stan <stanb(at)panix(dot)com> |
---|---|
To: | Olivier Gautherot <ogautherot(at)gautherot(dot)net> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Handling case variatiions on a user defined type? |
Date: | 2019-09-15 13:26:21 |
Message-ID: | 20190915132621.GA24445@panix.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Sep 15, 2019 at 09:58:45AM -0300, Olivier Gautherot wrote:
> El dom., 15 de septiembre de 2019 09:37, stan <stanb(at)panix(dot)com> escribi??:
>
> > I have several enumerated types that look like:
> >
> > CREATE TYPE confidence_level AS ENUM ('HIGH' ,
> > 'MEDIUM' ,
> > 'LOW' ,
> > 'WAG');
> >
> >
> > I have someone creating data for this project in spreadsheets, and then am
> > importing the data using \copy.
> >
> > Problem is the data in the spreadsheets is entered in mixed case.
> >
> > Is there a way that I can use the type itself, to enforce something like a
> > to_upper(). Or is there a better way to "human proof" this?
> >
> > --
> > "They that would give up essential liberty for temporary safety deserve
> > neither liberty nor safety."
> > -- Benjamin Franklin
> >
>
> What about a trigger on INSERT, which would enforce the case?
That sounds like a good idea, thanks.
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
From | Date | Subject | |
---|---|---|---|
Next Message | stan | 2019-09-15 15:33:09 | Shouldn;t this trigger be called? |
Previous Message | Olivier Gautherot | 2019-09-15 12:58:45 | Re: Handling case variatiions on a user defined type? |