[prev in list] [next in list] [prev in thread] [next in thread]
List: mysql
Subject: mysql: Transactions and MySQL
From: "aaron" <ross () forum ! swarthmore ! edu>
Date: 1998-08-31 12:53:03
[Download RAW message or body]
Hi,
I was hoping I could get some advice. I am in the process of creating a database \
backend using and DBI for a group of web sites. I am very happy with mySQL's speed, \
ease of use and support (i.e. this mailing list and its archives). However I am a \
little concerned about not having a transaction based database server for a busy web \
site. I was wondering what solutions other people had come up with. I've read the \
docs and I wasn't entirely convinced that updating fields "relatively" would solve \
the problem of conflicting client threads. I'm not worried about id fields, \
auto_increment is great. What concerns me is what happens when 30 or 40 updates and \
inserts happen at once. I don't know how often it will happen that they occur at \
exactly the same time, but I am certain to get 30 to 40 at nearly the same time due \
to the nature of the website. Won't LOCK table slow things down a lot? Having to \
lock files is a part of the problem we are trying to solve by moving to a SQL \
database system. But then again transactions would probably slow things down too.
Any advice will be greatly appreciated. Aaron.
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META content='"MSHTML 4.72.2106.6"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT color=#000000 size=2>Hi,</FONT></DIV>
<DIV><FONT color=#000000 size=2> I was hoping I could get some
advice. I am in the process of creating a database backend using and DBI
for a group of web sites. I am very happy with mySQL's speed, ease of use
and support (i.e. this mailing list and its archives). However I am a
little concerned about not having a transaction based database server for a busy
web site. I was wondering what solutions other people had come up
with. </FONT></DIV>
<DIV><FONT color=#000000 size=2> I've read the docs and I
wasn't entirely convinced that updating fields "relatively" would
solve the problem of conflicting client threads. I'm not worried about id
fields, auto_increment is great. What concerns me is what happens when 30
or 40 updates and inserts happen at once. I don't know how often it will
happen that they occur at exactly the same time, but I am certain to get 30 to
40 at nearly the same time due to the nature of the website.</FONT></DIV>
<DIV><FONT color=#000000 size=2> Won't LOCK table slow things down a
lot? Having to lock files is a part of the problem we are trying to solve by
moving to a SQL database system. But then again transactions would probably slow
things down too.</FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT> </DIV>
<DIV><FONT color=#000000 size=2> Any advice will be greatly
appreciated. Aaron.</FONT></DIV></BODY></HTML>
-----------------------------------------------------------
Send a mail to mdomo@tcx.se with
unsubscribe mysql your@subscription.address
in the body of the message to unsubscribe from this list.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic