Linguistic comparison - When is it required

Question

I have a question if linguistic comparison is required with operators like =
Also lets assume that I am not interested in performing a case insensitive or accent insensitive search.
My query may be something like
Select * from test where name = '{Japanese_Name}'
It looks like for cases where you are not interested in case or accent insensitivity there may not be a need to use linguistic comparison with = operator. Is this assumption correct.

Answer 1

I think all the document tells us is that NLS_Sort applies to = operator when NLS_Comp is set to Linguistic.
It still leaves us with the same open question of whether there is a need to make a query linguistic if it does not need to be case or accent insensitive. ( Once again this question is only for operators that perform exact string matches like the = operator)
The reason why this question is so important to me is, like I have posted in a different forum, I need to minimize the amount of changes we need to make to our sql queries. We have a lot of queries that are using the = operator on a column that stores multilingual data. I do realize that we can alter our session to set NLS_Sort and NLS_Comp and do not really have to change our queries. But making queries linguistic comes at a performance cost. We need to make sure that all the linguistic indexes exist and plus do additional performance testing.
I would not want us to go through all this effort only to find out there was no need to make these queries linguistic in the first place.