in reply to Re^2: Perl concurrent access
in thread Perl concurrent access

Not necessarily. If it is just a query (select), rather than an update, delete, or insert, then locks might not be involved. I meant the term "transaction" to be technical, that is possibily involving a lock. So it depends on the type of transaction, and the database. Some databases require table locking and some row locking. Some databases have different requirements depending on the table type (MySQL comes to mind).

This still assumes that the jobs are running concurrently. Are they?
It might also help if we knew the OS and which database product.

Replies are listed 'Best First'.
Re^4: Perl concurrent access
by TienLung (Acolyte) on Sep 10, 2009 at 14:12 UTC
    It is just a select. The database is MySQL client version: 4.1.22. I just ran made 4 requests at the same time, and looked at the processes in the CPU. The perl script in question appeared 4 times in the cpu process list, each entry using a similar amount of CPU and Memory. The OS is linux i686 running apache 2.0.61.
[reply]
      OK. Are you doing anything else in your script? If not, then it is time to look at the query.
[reply]

In Section Seekers of Perl Wisdom