Thanks for reply.

1. Yes. I really need multicolumn primary keys, because I have such DB scheme and I think there's no way out.
Suppose you have a bug with many legs: BUG(id(pk), name)---*LEG(bug_id(pk1), leg_number(pk2), length)
Is there another possible method to do such scheme? One-to-many relationship.
2. I'm using MySQL 4.x. Transactions is not too much concern me, cause I'll have only one SELECT'er and only one INSERT'er in my DB. Autocommit will satisfy me, I suppose. Maybe later I'll switch to MyISAM engine.
Referental integrity is not to shoot myself in foot, while filling mapped structure and then saving it into DB. But I think relationships (many-to-one, one-to-may, one-to-one) is sufficient.

In reply to Re^2: Persistence framework for MySQL 4.x (InnoDB) by mman
in thread Persistence framework for MySQL 4.x (InnoDB) by mman

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.