Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Neato, simple BLOB support is one of two things I've been waiting for to add SQLite to a system of mine.

    Maybe you can start thinking about the other one.... sequences.

    The big problem with sequences is that they need to happen outside of any transactions. With MySQL, you can emulate sequences quite nicely (DBIx::MySQLSeqence) by using a different connection and that way keep it out of transactions (sequences can NEVER be allowed to rollback).

    Except I _think_ that concurrency issues in SQLite make that solution impossible. You can only lock the entire database at once right?

    So if you need to fetch a sequence in the middle of a transaction, you can't just use another connection because it can't increment the sequence until the transaction ends...

    Now, one answer is to add a second SQLite database, but that really really complicates things and what might work as a one-off hack in a single case doesn't really generalise at all well.

    So any thoughts?