Hi, What will happen is that the rdbms will lock the row for you, updates it and unlock it. This is transparent for the user.
there will be a wait (not a problem) if another user want to update the same row. When the first transaction is committed, the second can hold a lock for update. There is only a problem if each transaction waits for the rows modified by the other transaction to commit (deadlock). Mathias Selon [EMAIL PROTECTED]: > Hi! > > If there is no any lock at all while one update a row, what it is going to > happen to my SQL database? In which cases, it might cause problems? Anyone > know? > > Thanks > > __________________________________________________________________ > Switch to Netscape Internet Service. > As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register > > Netscape. Just the Net You Need. > > New! Netscape Toolbar for Internet Explorer > Search from anywhere on the Web and block those annoying pop-ups. > Download now at http://channels.netscape.com/ns/search/install.jsp > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
