comment on

I think that if disk space is an issue, then memory would be and issue also.

You'd think so! But I actually usually have less disk space available than I have RAM. The old adage that there isn't a HD you can fill to the brim with random bric-a-brac in three weeks' time is still true.

That said — the SQLite DBs I've encountered so far aren't that big, no; on the order of (tens of) megabytes, which wouldn't be an issue even for me. OTOH there's no a priori reason they couldn't be (much) larger.

Being that you only have to extract the SQLite DB file and have complete control over where it goes, it should be pretty easy to identify, extract, operate on and then delete that single file. (But maybe I am missing the point?)

No, you got it nailed. I was really only asking because I'm too lazy to put in even that much work!

In reply to Re^2: Accessing SQLite databases within ZIP files by AppleFritter
in thread Accessing SQLite databases within ZIP files by AppleFritter

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks