|
|
Posted by Knut Krueger on 11/27/07 07:16
Jerry Stuckle schrieb:
>
> Damn youngster. I was programming a good 15 years before that. Try a
> mainframe with 4,000 bytes (not 4K) of core memory and clock rates in
> the 100's of kHz range. That describes the first system I was on.
>
> But those days are long gone.
>
>> 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.
>
Hi Grandpa ;-)
maybe you did some programming of VGA interfaces with more than on 64 Kb
segment in the past. It was a common and good style do disable the
integer overflow error during direct writing into the memory. (means for
1 line of code)
Why? The program needs *after* writing in the memory, therefore after
the integer overflow the branch to switch the memory page.
Preventing the error before would cause double and useless if -else
branches and would slow down the system.
That's my biggest part of knowledge and I am still programming those old
machines, because they are still in use and partially non exchangeable.
Back to SQL (and that's not my filed of expertise): I have one sql query
where normally (means nearly 100%) is an result after the sql query. I
have to branch depending on the results.
Why should I branch to the same code with an additional SQL query before
instead of suppressing the error and using one big switch case selection
and one of them is the error branch. In both cases there is an used and
working error procedure.
It is the individual responsibility to use the @ in very minor cases and
thinking about the consequences, but back to the OP in this case I
would agree to determinate whether there is better to determinate before
whether it is INSERT, UPDATE or DELETE. This would use the right
resources for that branch
> Do you see a performance problem?
I was told form owner of an internet server farm that there are
performance problems on shared internet server, and on standalone with
hundreds of parallel accesses, especially in the MySQL part.
In his mind they could be minimized with better coding, means using the
queries in the very important branch, without losing of security.
Regards Knut
Navigation:
[Reply to this message]
|