Horst Herb wrote: > > > I think this is a quite workable solution for some systems. I haven't tried this yet >(but I will sap) - but the first thought that comes to my head: one more table for >each list for each doctor - a hell of a lot of tables. Probably each of them indexed >as well. Here goes my cache, my RAM..... =8-0 Wouldn't I be worse off at the end of >the day? Will tell you when I have tried. > Well, this all is stored on the server side, where table space and index space is not much of a limitation. While we tend to use faster and more expensive disks on our Oracle database system, Quantum is selling network disk appliances with 120 Gig of space for $3000. Disk and main memory are just not limitations on the server side anymore.
- Re: Real world problem: pick lists in medical softwa... Thomas Beale
- Re: Real world problem: pick lists in medical s... Horst Herb
- Re: Real world problem: pick lists in medical s... Wayne Wilson
- Re: Real world problem: pick lists in medical s... az
- Re: Real world problem: pick lists in medical s... Wayne Wilson
- Re: Real world problem: pick lists in medic... Horst Herb
- Re: Real world problem: pick lists in m... Wayne Wilson
- Re: Real world problem: pick lists in medical s... Horst Herb
- Re: Real world problem: pick lists in medic... Alvin B. Marcelo
- Re: Real world problem: pick lists in medical s... Daniel L. Johnson, MD
- Re: Re: Real world problem: pick lists in medic... jeff b
- Re: Re: Real world problem: pick lists in m... Horst Herb
- Re: Real world problem: pick lists in m... Wayne Wilson
- Re: Re: Re: Real world problem: pick lists in m... jeff b
- Re: Real world problem: pick lists in medical s... Falball
- Re: Real world problem: pick lists in medical s... Adrian Midgley
