Thank you erix for your helpful reply. I am using MySQL.

- It seems unwise to name a table with 'index' or an '_index' suffix.
Noted - I will change

- ...Concentrate on getting easy-to-understand queries.
This is exactly what I am trying to do as I know some one else will be maintaining.

- Your option 2 (everything in one table) is called EAV and is generally frowned upon.
Thanks for the links, and yes Option 2 seems to be a bad idea.

Maybe you should try to show us the SQL-'hairiness' that you fear. It probably isn't as bad as you think :)

I don't have any hairiness at the moment, what I have is a Perl loop which queries each table in turn:

my ($self,$params) = @_;
my %tables = (
    origin      => 'tree_origin',
    category    => 'tree_flowering',
    ripe        => 'tree_ripe',
    usage       => 'tree_usage',
);
my $ids;
for my $name (keys %tables) {
    my $value = $params->{$name} or next;
    $ids = $self->search_index_table( $tables{$name}, $value, $ids );
    last unless $ids;
}

[download]
And the sub to query the database is something like this... 
sub search_index_table {
    my ( $self, $table, $value, $ids ) = @_;

    my $query = "SELECT id FROM $table WHERE name=?";
    if ($ids) {
        my $id_string = join(',', @$ids );
        $query .= " AND id IN ($id_string)";
    }

    my @results;
    my $dbh = $self->{'dbh'};
    my $sth = $dbh->prepare($query);
    $sth->execute($value);
    while ( my ($id) = $sth->fetchrow_array() ) {
        push(@results,$id);
    }
    return (@results ? \@results : undef);
}

[download]
This all works correctly, but I can't help thinking that all these calls to the database server (which is on another machine) is very inefficient. I suppose my real itch is that there are only a couple of hundred rows in the main table, and I have another 10 or so tables to index the multiple-valued fields - from my reading this seems the correct way to do things, but at the same time feels over-engineered for such a small dataset.

In reply to Re^2: OT - SQL choosing a schema for index tables by bangor
in thread OT - SQL choosing a schema for index tables by bangor

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.