Re: Multi-Language data

Goeff,
Some thoughts on your problem...

1. you could try a UNION in which the first Select is the desired language and the second select is for the default language...only one will be true at any time. Select a,b,c from tbl where lang = 'F' <-- or bind variable ... other parts of where clause... UNION ALL Select a,b,c from tbl b Where lang = 'D' <- default langauge ... other parts of where clause... and NOT EXIST (select 'x' from tbl c where lang = 'F' <-- or bind variable ... other parts of where clause ...)
2. Create a stored function to determine the proper language code, 'F' or Default. Then use the function in the WHERE clause. I think however, that using function in the WHERE might cause index not be used (...comments anyone?...)

Create Function TheLangCode

   (DesiredLang varchar2,
    DefaultLang varchar2,
    a,b,c,d all the other variables needed to define the select...) Return Varchar2 is
  x char;
Begin
  Select 'x' into x
  From tbl
  Where Lang = DesiredLang
  And ....a,b,c,d...other parts of where clause...;

• success... Return DesiredLang; Exception when no_data_found Then Return DefaultLang; End;
  • now, the select Select q,r,s,t from tbl where Lang = TheLangCode('F','D', .... other fields...) and ... other parts of where clause ...;

Good Luck
Robert Proffitt
Beckman Coulter

In article <84v64t$77r$1_at_quince.news.easynet.net>,   "Geoff Munday" <geoffm_at_qsiuk.com> wrote:
> We have a need to present data in a multi language form
> eg
> SELECT SOMETHING FROM TABLE WHERE LANG='F' ....
> will give SOMETHING in the correct language.
> If there is no data in F(rench) then the default language version
should be
> returned.
> Our first thought was to split the original table into a language
> independent part and a
> language dependent part and select from a view using
> NVL(B.SOMETHING,A.SOMETHING).
> This will not work when it comes to an UPDATE.
>
> As far as I can see NLS does not relate to data and so will not help
in this
> matter.
> From what little I have found I suspect that TYPE or the text
cartridge may
> form part of a solution.
> Does anyone have any ideas?
>
> What we would ideally like to do is present data to a user in his own
> language with
> no restrictions in UPDATEs, INSERTs and QBE.
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Wed Jan 05 2000 - 11:00:02 CST