sql - DML generated at front-end vs. Insert - Update - Delete performed by stored procedures -


To think about the real benefit of the DML command (inclusion, updating, deletion) in the database through stored procedures for simple CRUD, I

Applications. What if the use of some generic procedures in the front-end producing DML command, what is the benefit of that application?

According to the performance, you are not likely to see any benefit. I think this is more about the security of the database.

The advantage of procedures stored in any situation has different potential for controlling the security of data for DBA, this is often the priority call by DBA. Entering the CRUD on the server in the server means that it controls 100% access to the server. Your code must match your stored proc "API".

If you include logic in Visual FoxPro code through Remote View, Cursor Adapter, or SQL Pastthrough SQLXAC (), it means that you have 100% code control and DBA will give you the database The components have to be accessed, or through the application roles you use for connection codes. Regarding building a CRUd SQL statement on the fly, your code may be slightly more flexible. The stored work will normally have to handle the flexible parameters to make a statement.

Rick Chamber


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -