(Chapter 10) Attached: List the three main approaches to database programming. What are the advantages and disadvantages of each approach?
Instructions: Your response to the initial question should be 250-300 words. Next respond to two postings provided by your classmates. The first post should be made by Wednesday 11:59 p.m., EST. I am looking for active engagement in the discussion. Please engage early and often. You are require to create your initial thread in order to view and respond to the threads posted by other students. There must be at least one APA formatted reference (and APA in-text citation) to support the thoughts in the post as needed. Do not use direct quotes, rather rephrase the author’s words and continue to use in-text citations.
List the three main approaches to database programming
There are several approaches to database programming, three points out of that are:
- Designing or building a brand-new language.
- Properly utilizing the database function library.
- Embedding the commands associated with database into a basic-purpose programming language.
What are the advantages and disadvantages of each approach?
The advantages and disadvantages of each approach is:
Inquiry linguistic structure can’t be checked at assemble time, conceivably mediocre execution.
It is difficult to reuse existing code written in more famous dialects; DB programming dialects regularly do not “feel” like a “genuine” programming language; absence of IDEs.
No powerful questions; requires language explicit pre-compiler; needs explicit IDE support.
Simple to use (for static questions); inquiry punctuation can be checked at order time.
No impedance befuddle; potentially execution benefits because of DB reconciliation; sentence structure check at incorporate time.
For the most part autonomous of the programming language utilized; permits dynamic questioning, in any event, utilizing different information base associations; great instrument support (utilization of libraries is now covered by standard functionalities of IDEs)
List the three main approaches to database programming. What are the advantages and disadvantages of each approach?
The three main approaches of database programming include the technique which is a precompiled bunch of SQL statement(s) that is put away on the data set worker. The SQL proclamations are constantly executed on the information base worker. Put away strategies have for quite some time been a decent method of allowing the worker to handle your information. They can altogether lessen the responsibility on the customer, and once you become more acquainted with them you’ll think about how you at any point oversaw without them. There is absolutely more to a put away strategy than just referenced, however I do think this is the main part of a put away methodology (Reese, 2000).
Consider everything: it’s a way of collection a cluster of SQL articulations, putting away it on the data set server, and executing it’s anything but a solitary call. The way that the put away methodology is pre-accumulated will save you time also when executed. Moreover, the put away method can be executed by quite a few clients, which means you may save a ton of transmission capacity just by calling the put away methodology as opposed to sending the entire SQL explanation each time. A put away strategy can contain any SQL articulation that your information base worker can comprehend. This implies you can utilize put away techniques for different tasks, such as executing inquiries both purported activity questions, for example, DELETE inquiries, and column returning questions, for example, SELECT statements (Leontiev et al, 2002).
Another task you can utilize a put away methodology for is data set support. Use it to run clean up SQL explanations when the worker is least occupied and consequently save the time and exertion of doing this physically. I will not cover support errands in this part, yet they are significant, and you ought to know about the different undertakings you can perform with put away systems. In case you’re similar to me, you have been or are working for a little organization that doesn’t have an information base head, in which case you’re accountable for keeping the data set worker running. In all actuality, it’s anything but an optimal circumstance, however you surely become more acquainted with your DBMS in unexpected manners in comparison to you would simply being a software engineer, and that is not terrible by any means (Ohori & Ueno, 2011).
Leontiev, Y., Özsu, M. T., & Szafron, D. (2002). On type systems for object-oriented database programming languages. ACM Computing Surveys (CSUR), 34(4), 409-449.
Ohori, A., & Ueno, K. (2011, September). Making Standard ML a practical database programming language. In Proceedings of the 16th ACM SIGPLAN international conference on Functional programming (pp. 307-319).
Reese, G. (2000). Database Programming with JDBC and JAVA. ” O’Reilly Media, Inc.”.