|
Posted by Knut Krueger on 11/25/07 11:22
> CPU cycles have nothing to do with it. This is all about good
> programming techniques.
>
sure are CPU cycles and therefore SQL queries a question especially at
an internetserver.
> It is much better to not make the call you know is going to cause an
> error in the first place. The way you're doing it is just sloppy
> programming. Such techniques are problems just waiting to happen.
If the record is more than 50% available, then there are less sql
queries with the suppress error method otherwise with the other method
is better.
I started programming with assembler and 8068 processors and in this
time everybody must take care about CPU and memory usage.
And if the CPU usage (means CPU instructions) was less with suppress
error it was a must to use this. That's why it is possible to suppress
errors.
In both cases the error handling was important but it was in different ways.
and using the @ including an error handling should not a bad programming
style if the usage of the server is more less.
Therefore I my mind there is still the question which way is with less
cpu usage. That's not the question for one user, but for 1000 users
simultaneously
Regards Knut
>
Navigation:
[Reply to this message]
|