|
|
|
|
|
|
by JonM
5961 days ago
|
|
|
"ramifications of poorly-constructed SQL" Surely the best defense against this is writing every query yourself rather than letting Rails do it? (As implied in the article). My argument isn't Ruby execution speed vs PHP execution speed, it's Ruby writing it's own SQL vs me writing it. I agree 100% that the database is usually the bottleneck, it certainly is for my site. |
|
|