I think SQLite db files are binary cross platform, but possibly not across versions. I guess you'd have to check the SQLite manual for that.
That does sound a bit fragile in any case, so the DDL might be a more solid choice.
You can put data files next to where your module source gets installed. Find out where that is:
package Your::Module;
use Path::Class;
# Return ".../site_lib/Your/Module/data/sample.sql"
sub sample_db_file {
file( file(__FILE__)->dir->absolute, "data", "sample.sql") . "";
}
If you use Module::Build, you need to specify that nonstandard file extensions should be packaged, like this:
# Build.PL
$builder->add_build_element('sql');
Not sure about the EMM or Module::Install incantations.
So you'll need to create a .db file in a convenient (for the user) writable location. File::HomeDir might be useful for finding that location.
/J
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.