Thinking about the reconstruction---of the computer room caused by combinatorial query

Objective:

Do not code-based programming, software design based on graphics.

---Miss mi

As Mentionedabove, is the last Thursday night when the door lock in the small meeting room to hear the teacher to nine period brother Siang the system when the words, let me very touched. Why?

There is a question do not know people think about, for example, in the "design mode" learning process, we follow the code "divert" like the code knocked out, it seems that they really understand, but really let oneself to practice, we can make it? Or in the machine room, some of the difficulties we are imitating "predecessors" blog made out, the program can run up, the code himself also understand, feel success, but these things really become yours?

For combinatorial query, I have my own idea before design, by setting global variables to pass SQL statements, that is, the SQL statement is in the U layer by selecting the drop-down menu after the "stitching" good, by uploading to the global variable, the D layer of the SqlHelper function to go, Then follow the old way back to the DataTable table shown on the DataGridView control, when doing according to their own ideas, found that 1, U layer logic judgment is very large, and with the escape function, and so on, the vast majority of code in the U layer, B, D, is to go a form just, This is not as good as directly in the U-level write CONNSTR connection database ... 2, other people use the template method, stored procedures I do not know how to use, although the design mode to see two or three times, the data stored in the process is also online search ...

What to do? Search information (blog), my portfolio query reference Xu Fengzhu blog, Shao brother Siang blog, ianteo brother Siang Blog ..., the principle is basically the same, through the " specific query class to inherit the parent class template, the parent class to the Appearance class, B-Layer object instantiation, walk seven layers of routines, The only difference in calling the Query method in the D layer is that the sql= "Combinequery" (the SQL statement into a stored procedure), and the other seven-layer old routines, so that the two two-point "template methods" and "stored procedures" in the process are well applied to the system.

This blog, will not be specific to show the code, everyone's code is very similar, I would like to talk through the combination of how to turn someone else's code into their own things, how "divert", a very good way to say "based on graphics programming, there is a picture of a click-click Code Close the eyes came out."

As shown in Theabove figure, the big frame is 7 layers of thought, according to the old routine, create interfaces, D layer, factory, BLL layer, appearance, U layer, then focus on the U-layer how to reuse the parent form, how to call the stored procedure in the D-layer SQL statement, And in the database will be flexible to use the stored procedures to write out, this is the most important, I think the idea of programming, the idea is more important than the implementation of the Code, to draw on other people's things, to clean up after the context of their own picture, so in the code, knocking similar code, and even in the interview, You have this picture in your mind, the interviewer asks what, you can go directly to the map to find the information you need, instead of divert the way you thought.

It is written that there is no technical aspect of the discovery, but I think that these are more how to play, improve the technology of an overview, combinatorial query, nothing difficult.

Thinking about the reconstruction---of the computer room caused by combinatorial query