comment on

TomKane:

Just replacing the DLL isn't going to work because the API is slightly different. For example, how would DBD::SQLite know how to send the key to the dll? I'd think your best bet if you know C and perl would be to look at the installation package and see how hard it might be to add sqlcipher to the package. I'm guessing it would be fairly straightforward, but you'll have to spend some time to figure out how the module builds, build some test cases and such.

Failing that, you could offer to pay the maintainer to do the integration for you, or pay someone to create a patch for you.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

In reply to Re: sqlcipher for sqlite by roboticus
in thread sqlcipher for sqlite by TomKane

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.


Think about Loose Coupling
	PerlMonks