Date: Sun, 23 Mar 2008 19:09:15 -0500 From: Paul Schmehl <pauls@utdallas.edu> To: Da Rock <rock_on_the_web@comcen.com.au>, freebsd-questions@freebsd.org Subject: Re: OT: (Way OT) PHP and MySQL concurrency control using MyISAM tables Message-ID: <EB60345E777EA5DAC897208A@Macintosh.local> In-Reply-To: <1206313415.6973.78.camel@laptop2.herveybayaustralia.com.au> References: <1206313415.6973.78.camel@laptop2.herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--On March 24, 2008 9:03:35 AM +1000 Da Rock <rock_on_the_web@comcen.com.au> wrote: > I know this is not quite the list for these things, but I tried the PHP > list and got no reply whatsoever. In fact, I don't think anyone's home > cause the entire list is silent... > > I'm trying to setup a system using web apps in PHP using MySQL as the > backend database, only this time I need transaction services. According > to the PHP manual if a transaction is served for MySQL it can come back > as committed even though it may not. So what I'm trying to accomplish is > develop some row level locking with the PHP script. > > I enquired about setting up a servlet (for want of a better term) with > PHP, something that will serve the requests of the rest of the app. To > be honest though, I'm not entirely sure how to approach this. > > Any ideas would be very welcome. > Following list etiquette, I'm replying to you and the list. I believe that postgresql has transaction locking. You might consider using it instead. Mysql is supposed to have transaction locking in version 5.1, but I haven't tested it and don't know how robust it is. Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EB60345E777EA5DAC897208A>