Join might be better than subquery. And as far as I can see, that data.key can be multiple with ors or even in and like/ilike should work also.

I have tables empty (=just couple of lines) and subquery is faster than window-join. 1.1ms vs 1.4ms. No indexes. Postresql v8.4.22, Debian 6.0.10

Usually there should be vacuuming of some kind. Just transfer old to history.

Do you have any projects in mind, where Perl-code is stored in db?

There is ofc limit how much views etc one should put to db. Sometimes it's better to do with code than in db.
Views are nice, when you want to limit permission of some user. There are few things in on update and on delete.

In reply to Re^8: How to interpolate sql-output by Seq
in thread How to interpolate sql-output by Seq

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.