SQL or components?

Today, write several functions at the time, involving the main additions and deletions from the data, we need to consider the constraints between the master and slave, but also consider closely related to database storage but business-related keys (such as ID field) of storage, Although not difficult, but it takes time and manual labor.

Then the brain suddenly flashed a thought, that I was not stupid out, wrote a half-day function, that is what a SQL statement, why do I still Ku Haha write function? Since I use a database, why also made their own wheels to achieve database the most most basic and most efficient functions? Well, if not silly also not far from stupid.

Mindset is terrible, with Delphi database components, very, very easy access to data, but also the next logical operational data continue to use it? The problem is this appropriate?

SQL and components are two hands, which hand do what is appropriate, or to distinguish better. One or two simple update value, with easy assembly, more complex data modification, or use more appropriate SQL.

Guess you like

Origin blog.51cto.com/bigdata1024/2432811
Recommended