comment on

Yes and no.
DB_File.pm is not thread safe.
Neither is BerkleyDB.pm

The strategy with DB_File is to blessed(%hash)->flush after writing, and to retie before reading to ensure you got the latest data.

This will work fine but only if you use a newer version of BerkleyDB (anything about 2.5 will work fine with this technique).

If you want better transaction control, use BerkeleyDB.pm, and you got access to the full api (just go buck wild).

You other choice to consider is DBD::SQLite.

If any of this is too slow for you, you can always use Cache::Cache

MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: How to share huge data structure between threads? by PodMaster
in thread How to share huge data structure between threads? by ph0enix

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