This post is not maintained.
Please check my blog-post at : http://dhruvb.com/blog/node/3 for updated details.
Many friends of mine have questions and doubts regarding the “Specialized Syntax based Query Building” system. They would, however, prefer the “Form-based Query Building”. Why do we need such a system, when the conventional system is working fine ? Why does the user have to type a “Specialized Syntax”, can’t he just use SQL ? and many more questions arise. Lets consider the following scenario :
“A local newsletter-based company has to keep a check on its members, their subscription details. But, they have no system in-place. But, now with the help of newly recruited young staff, they have started to grow. As their enterprise is expanding, they have now felt the need of a Members management system. The management staff, however, is a genius in management, but they are not so good at SQL or databases. So, they call their friend, who is also a developer to get the job done for them.”
The friend now, is lazy enough to start coding from scratch. He gets a Web Application framework, adds the required functionalities, tweaks them. Builds a form-based query system and the system is now good to go. The management likes the system, and they loved using it. Ahh !! But, why is the querying so restrictive “Why can’t I sort the data ? Why can’t I get the members of users in a country ? Where can I search for number of males in a state ?”. The developer is now left with two methods :
Method 1 :
Method 2 :
“This system, I have coded this plugin once. OK, it is based on a files, which contain the metadata required to build database queries. Also, the syntax file is defined. I don’t have to code again. If the system changes, its only the file that changes. It is simple for user to build queries with the suggestions given on runtime, good UX. That is cool.”
Let the developer decide, which method to choose !