comment on

As roboticus says - open two or more database connections (or client apps) and run requests with varying degrees of delays.

I presume that the transactional part of the system is handled at the database level. Even so, if Dbix::Class offers a high level of abstraction over what actually happens in the DB (something I don't know as I haven't used it) then you should be careful of things like deadlock situations where locks on different resources are acquired in a different order in two processes, and each process is waiting to acquire a lock that the other already holds.

And keep in mind that you are likely to find race conditions in places where you didn't think that they were likely to appear...

Michael

In reply to Re: Testing transactions by mpeppler
in thread Testing transactions by matija

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.


No such thing as a small change
	PerlMonks