[Wolves] SQL problem

Simon Burke its_simon_burke at hotmail.com
Wed Mar 17 11:13:58 GMT 2004


On 17/3/04 11:01 am, "sparkes" <sparkes at phreaker.net> wrote:

> On Wed, 2004-03-17 at 10:53, Simon Burke wrote:
>> On 17/3/04 10:35 am, "Chris Procter" <Chris at foxonline.co.uk> wrote:
>> 
>>> I'm a bit confused, are you trying to hold two copies of the same info, one
>>> in english and one in welsh? If so could you use two fields in the table e.g
>>> english_text and welsh_text and then pick which column you want on the fly
>>> (dependant on some variable set by the front end)
>>> i.e. "SELECT " & language & "_text FROM table"
>>> with language = "welsh"
>>> 
>>> Or have I missed the point?
>>> 
>>> chris
>>> 
>> True true, the only problem we have is that data needs to e interchangeake
>> between the both, so we need the ability to translate between the two,
> I think you misunderstood Chris' answer.
> 
> What was suggested was the data table contains the english and welsh
> text along with the data associtated with it.  This way you can grab
> either the english or welsh (or even both if you want) whenever you
> select data from the table.
> 
> sparkes
> 
> 
Ahh. Oakies. In that case, then the problem is simply that there are both
english and welsh users and they both input in their own language, but we
need the ability of say the english to access the welsh data but read it in
english, and vice versa




More information about the Wolves mailing list