Chris and Jay:
Thank you both very much for your comments; that solves it. I am not
a trained database designer, but I have resources on normalization; I
simply neglected to consult them, thinking that this was a SELECT
problem, not a design problem. Your input was just what I was hoping
On Mon, Jun 01, 2009 at 09:21:40PM -0700, Craig Smith scratched on the wall:
> Hello:
>
> I have about 3000 electronic images that I am preparing to distribute
> to my family members. They use a variety of operating systems, so I
> am providing the images on remote hard drives, with the
What's wrong with a properly normalised schema like this:
create table main (id, name,...);
create table keyword (id, label);
create table crossref (id_main, id_keyword);
The concept of core and other keywords is a bit arbitrary.
What is important (i.e. core) today might not be so tomorrow.
Hello:
I have about 3000 electronic images that I am preparing to distribute
to my family members. They use a variety of operating systems, so I
am providing the images on remote hard drives, with the images divided
into folders based on years the images were created. All images were
4 matches
Mail list logo
