Jump to content

Post-insert calculations in self - a bad idea?


vineld

Recommended Posts

When I have a MySQL field that is a result of two or more others (it is sometimes a good idea to store such value as well even if it is redundant data) I usually do the math in the same sql sentence like this:

 

UPDATE tbl SET f1 = f1 + 1, f2 = f2 + 7, f3 = f2 * f1/3 WHERE blabla

 

This has seemed to work so far but I can't help but wonder if this code is secure or is there a risk of a faulty f3 value?

What I am thinking is this:

 

1. The operations f1 + 1, f2 = f2 + 7 will have to be done first.

 

2. f3 will then have to be calculated using the two first fields.

 

The question is really this one:

 

Is this particular row locked while doing all three operations and will the last one always be done last in a query?

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.