vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am working on a website with two applications on the server - both accessing the MySql database. PHP applications are reading and writing to the database and a Java servlet (running under Tomcat) is also accessing the database. Currently the software in both applications is under development so there is very little in the way of actual database accesses, however, someone has suggested that we will have problems in the operational system because both Java and PHP applications will be attempting to access the same database. My understanding of MySQL is that it can handle these accesses without a problem. I would appreciate any comments on the potential problems that we might see. Thanks, Mike |
| |||
| On 17 Jan 2006 13:00:53 -0800, "Mikey" <mike.gunn@comcast.net> wrote: >I am working on a website with two applications on the server - both >accessing the MySql database. PHP applications are reading and writing >to the database and a Java servlet (running under Tomcat) is also >accessing the database. Currently the software in both applications is >under development so there is very little in the way of actual database >accesses, however, someone has suggested that we will have problems in >the operational system because both Java and PHP applications will be >attempting to access the same database. > >My understanding of MySQL is that it can handle these accesses without >a problem. > That's correct. Two apps accessing should be fine. Two instances of PHP or TWO instances of a Java servelet wouldn't be much difference than one of each unless the database isn't set up to handle locking. >I would appreciate any comments on the potential problems that we might >see. Just make sure you use proper locking so both apps (or more than one occurance of the same app) try to modify the same record at the same time. -- gburnore at DataBasix dot Com --------------------------------------------------------------------------- How you look depends on where you go. --------------------------------------------------------------------------- Gary L. Burnore | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ Official .sig, Accept no substitutes. | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ | ÝÛ 0 1 7 2 3 / Ý³Þ 3 7 4 9 3 0 Û³ Black Helicopter Repair Services, Ltd.| Official Proof of Purchase ================================================== ========================= |
| ||||
| Thanks for your comments, Gary. Gary L. Burnore wrote: > On 17 Jan 2006 13:00:53 -0800, "Mikey" <mike.gunn@comcast.net> wrote: > > >I am working on a website with two applications on the server - both > >accessing the MySql database. PHP applications are reading and writing > >to the database and a Java servlet (running under Tomcat) is also > >accessing the database. Currently the software in both applications is > >under development so there is very little in the way of actual database > >accesses, however, someone has suggested that we will have problems in > >the operational system because both Java and PHP applications will be > >attempting to access the same database. > > > >My understanding of MySQL is that it can handle these accesses without > >a problem. > > > That's correct. Two apps accessing should be fine. Two instances of > PHP or TWO instances of a Java servelet wouldn't be much difference > than one of each unless the database isn't set up to handle locking. > > >I would appreciate any comments on the potential problems that we might > >see. > > Just make sure you use proper locking so both apps (or more than one > occurance of the same app) try to modify the same record at the same > time. > -- > gburnore at DataBasix dot Com > --------------------------------------------------------------------------- > How you look depends on where you go. > --------------------------------------------------------------------------- > Gary L. Burnore | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ > | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ > Official .sig, Accept no substitutes. | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ > | ÝÛ 0 1 7 2 3 / Ý³Þ 3 74 9 3 0 Û³ > Black Helicopter Repair Services, Ltd.| Official Proof of Purchase > ================================================== ========================= |