After starting using XXFW for nearly half a year,I finally can not help writing something down about how and why I hate using it.Actually there are many problems I met when I was using it,and some of them are not only related with XXFW,but have something to do with the whole development workflow of the company.
I can not describe them all in one post,but I will try to write from an objective point of view.
one 100-line SQL VS hundred 1-line SQLs
From the view point of performance, this is out of question.Most time we will choose one 100-line SQL,because hundred 1-line SQLs' load burden will be much larger than one 100-line SQL.
What I want to discuss here is the maintenance part.“hundred 1-line SQLs” may be an exaggeration,but “one 100-line SQL” is not hard to imagine in XXFW at all.Actually, in the source code of XXFW systems,we can often find SQL sentences with 100~200 lines.
The problem is that it is really hard to read one SQL sentence,which has more than 100 lines,selects more than 50 columns by joining more than 20 tables,with different kinds of filtering conditions.Not to mention various structures and functions used in selecting columns.
In other words,this long SQL is written to do more than one thing by mixing lots of logic together.
In my opinion, because almost all XXFW systems are not so-large scale systems, user can feel no differences by changing one large SQL into several smaller SQLs.
But by doing this, the maintenance efficience will have a big boost,because every SQL will one do one thing with simple logic.And the whole source code will be much easier to understand.
The reason why many XXFW developers often write too-long SQLs is because of the structure of XXFW.It does not have the concept of MVC,so people can not encapsulate logic inside models.And without the encapsulation, the uint test or various auto test methods are far far away.
So here happens the funny thing:the intention that the first developer writing long SQL,is probably just for later easy maintenance,because he does not want to keep SQL sentences here and there without any methods of auto-test.However, the result goes to an opposite direction.the long SQLs is the main part of hard maintenance of source code.
2087
germansingergirl
izzy806
gummygunk