| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: turn off/on case insensetive search in Oracle DBMS
> Actually the most common workaround would be to include an uppercase
column
> for your searchable column and populate this with a before insert trigger.
> Current versions of Oracle also allow you to create an index on
> UPPER(column_name).
You've got to be kidding; actually have a duplicate column holding the data as uppercase ?. Now that takes the biscuit. What about if you want to be flexible enough (bad word for ORACLE that) to allow a user to search on any character field thay want - have a duplicate column for each - get real.
> Personally I'm of the view that the Oracle way is the correct way to do
> this, though I'll admit that others may and do disagree. For me data *is
> case sensitive in the general case. If you have a specific requirement you
> are better coding for it yourself. How do these other marvellously
flexible
> databases cope with the need for both case sensitive and case insensitive
> columns in the same application?
For fucks sake - How about you have a case insensitive string comparison routine...
"Other than that you could hit the CAPS key and then snap it off"... (I got that from the ORACLE manual)
FB
"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
news:3b6517ee$0$8513$ed9e5944_at_reading.news.pipex.net...
> "Andy Hallam" <ahm_at_exel.co.uk> wrote in message
> news:9jrs1g$16b$1_at_reader-00.news.insnet.cw.net...
> > Yes, you could do this - for most developers though this is totally
> > impractical.
> >
> > It's just another thing that ORACLE doesn't cater for...Ohh, sorry, I
mean
> > doesn't lower itself to the level of all the other RDBMS.
> >
>
> Actually the most common workaround would be to include an uppercase
column
> for your searchable column and populate this with a before insert trigger.
> Current versions of Oracle also allow you to create an index on
> UPPER(column_name).
>
> Personally I'm of the view that the Oracle way is the correct way to do
> this, though I'll admit that others may and do disagree. For me data *is
> case sensitive in the general case. If you have a specific requirement you
> are better coding for it yourself. How do these other marvellously
flexible
> databases cope with the need for both case sensitive and case insensitive
> columns in the same application?
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
>
> Legal disclaimer required by my employer
>
 |
 |