It is NOT simple to implement, it may seem like that because you've been tinkering with it a lot, but this shouldn't prevent you from noticing how many external dependencies and problem this introduces.

I find it highly disturbing to see you recommend such unholy measures, as as a high-flying Monk you're sure to sway lot's of unsuspecting youngsters to the dark side. I'm thrilled to see myriads of apps using SQL for iterating through lists and similar tasks.

Funny that you mention ugly interlocking problems and race conditions that you just wrapped in your bulgy sql libraries,

solution from Anonymous Monk(Re^4: How to tell a child what to do?) needs no interlocking-avoiding libraries, it's simple, REALLY self-contained ( and not, "well, kind-of self contained, when you factor in dependency on writable filesystem, enough place there, C-based sqlite library, with it's dependencies, correct sqlite file, with correct structure, and don't forget that when you change database format from 2.x to 3.0 your code will just die without en error message" ).

I don't know how you used SQLite that you never encountered those problems, but you've been very lucky and I envy you.

In reply to Re^6: How to tell a child what to do? by Eyck
in thread How to tell a child what to do? by Eyck

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.