 |
 |
 |
 |
|
|
|
Comments for: tim20010117
| Message # 1012884: |
|
Date: 08/13/02 07:12
By: Pedro Salgado Profile Subject: RE: Transaction in MySQL I dont know if this will help you but... On MySQL you can only lock the whole table. The statement is like: LOCK TABLES tablename READ (if your doing a SELECT on the table) LOCK TABLES tablename WRITE (if your about to do an INSERT or an UPDATE on that table) you could put always READ or WRITE after the tablename but the READ and WRITE operations have different priorities so maybe it would be best to put the right option for your action, unless you have a good reason for not doing so... If you use in the FROM clause something like FROM tablename AS tb1 the lock statement should be the same LOCK TABLES tablename AS tb1 READ To do a multiple table lock you should do LOCK TABLES tablename1, tablename2 READ To release the locks do a UNLOCK TABLES Just a final warning... when you test your queries and, for some reason something goes wrong, the locks persist so... it is better to have a error handler that always does a UNLOCK TABLES (imagine a site that had an SQL error and the tables became locked... unless you knew it, all of the data in those tables would become unreachable). Sorry for the length of the comment... hope it helps. PeSalgado |
Previous Message | Next Message |
| Comments: | ||
| full theory about database transactions ?? | Girish Agarwal | 01/27/05 00:36 |
| RE: excellent article | Lance Edusei | 07/14/04 08:30 |
| RE: MySQL Transactions | Rob Limbrey | 01/21/03 08:45 |
| MySQL Transactions | Imtiaz | 10/16/02 06:22 |
| MULTIPLE TABLES OR HUGE TABLES-BETTER OPTION? | Kapil | 10/06/02 10:48 |
| please found out my code mistakes | Mary Pei | 10/04/02 05:44 |
| project work please help us | mike smith | 09/11/02 06:51 |
| RE: Transaction in MySQL | Pedro Salgado | 08/13/02 07:12 |
| PostgreSQL nested transactions | Lonny L GRanstrom | 08/09/02 22:36 |
| RE: How to trigger Rollback | Vinco | 07/07/02 01:55 |
| How to trigger Rollback | Igor | 04/25/02 23:46 |
| What about batch updates? | pedro | 03/10/02 20:41 |
| LDAP "Rollback" | Fraser | 02/06/02 20:57 |
| nested transactions - my solution | Shivers | 08/17/01 12:57 |
| PHP, MSSQL7 and Transactions | Andrew Prior | 04/25/01 05:47 |
| XML and pgSQL | moses | 03/06/01 14:09 |
| RE: transactions... | george | 02/07/01 06:29 |
| transactions... | michael kristopeit | 02/05/01 11:35 |
| RE: MySQL Transactions | Ryan Ayers | 01/30/01 22:41 |
| Clean solution to nested transactions | Jeffrey Greer | 01/28/01 16:43 |
| RE: sessions and DB transactions | Kai Meder | 01/27/01 18:37 |
| RE: MySQL Transactions | Kai Meder | 01/27/01 18:35 |
| sessions and DB transactions | John Harnett | 01/26/01 23:17 |
| nextval/currval in postgres | Don Baccus | 01/26/01 20:54 |
| Transactions in functions vs. Postgres | Don Baccus | 01/26/01 20:46 |
| Re: I hate duplicate functions. | Kirk Parker | 01/24/01 19:20 |
| RE: nested xactions | Peter Moulding | 01/24/01 17:24 |
| RE: excellent article | Peter Moulding | 01/24/01 17:18 |
| RE: Transaction in MySQL | Mattias | 01/23/01 05:28 |
| RE: nested xactions | JBW | 01/22/01 23:37 |
| Transaction in MySQL | Habibi | 01/22/01 18:22 |
| MySQL Transactions | Ryan Ayers | 01/22/01 14:30 |
| excellent article | Ryan McGeary | 01/22/01 09:35 |
| nested xactions | Jim G | 01/22/01 08:48 |
| Ideas | Andrew Coldham | 01/22/01 03:49 |
|
If you are looking for help, please post on the appropriate forum here. Your questions will be answered much more quickly. | ||
