Friday, February 5, 2016

B5: Group B - Dianna Vogel

               SQL is the ‘Structured Query Language’ that is key for interacting with databases. [1] SQL is used to communicate with a database and relay specific commands. These commands can be used to update the information contained within the database, or draw certain information out. [2] The commands that are the life and blood of SQL are called ‘queries’. These queries start with a few basic functions, but when combined and expanded upon they become extremely comprehensive. A few of the most common commands accomplished with queries are: insert, select, create, etc… All databases start with a table and give the structure that queries need to work. Queries function based on codes, from simple to complex. A simple code would be to select a column within the desired table (as seen in Figure 1).
Figure 1. Sample Code for Selecting a Column
               This code could be expanded to include conditional statements in the where clause [1] to specify if the desired value is equal to, greater than, less than, etc. the referenced value. Once these skills have been mastered the same format can be used to create a new table, insert something into a table, manage records, or any number of things. The functions and code used to query within a database is the same platform of code used in other programs such as Matlab.

               SQL is important due to a number of reasons. One, it is one of the oldest programming languages. Many other programming languages have been modeled off of SQL and expanded upon. [3] Thus, it is not the easiest code to learn or use, because it seems almost primitive by today’s standards, but it is still incredibly useful. Likewise, due to SQL having so many other tools built off of it, it has almost become a universal language. SQLite is an SQL database that is used on Androids and IPhones, with some applications directly enabling its database. The universality of SQL creates the ability to code one program that will run on computers, phones, and anything else running SQL or SQLite. This type of interoperability is an idea fantasized by other software’s, like BIM.  Thus, the importance of SQL is its ability to transcend barriers and provide a platform to interact with almost any database

Citations
[3] http://sql.learncodethehardway.org/book/introduction.html

Comments

http://ae-510-ay15-16.blogspot.com/2016/02/b5-group-b-cummings.html
Comment to Bryan,

I agree that SQL is the platform upon which all websites have been built. This statement extends to the majority of programs, desktops, phones, and a full list of modern items. In relation to BIM, it is not surprising that SQL supplies the communication between the massive databases upon which programs like Revit run. The query command function allows the user to interact with different parts of Revit, including families. The family database is one of the most obvious databases within Revit. This database can be added to, selected from, and modified. Thus, I agree that SQL is a major part of BIM’s function, but I do not understand how it is a limiting factor. I believe BIM’s limiting factors come from other avenues.

http://ae-510-ay15-16.blogspot.com/2016/02/sql-stands-for-structured-query.html
Comment to Alex,

I like how you went into depth on how the queries work. The syntax is obviously important when coding a command for a database. If one comma, period, or letter is out of place the correct result will not come out of the query. This can make the process of querying complex and confusing to many people, which is why the user interface has been updated and reformatted in the programs built off of SQL. While these newer programs may be more user friendly, the importance of SQL has not faded. Without this initial language databases wouldn’t have made the progress they have made today.

5 comments:

  1. Dianna,
    I found your article very interesting and informative. I have used matlab before. After reading your article I also searched more programming software and found that some are much easier to use than others. I also was unaware that there are so many different types of programming languages.

    ReplyDelete
  2. Nice part about the importance of SQL. As mentioned, SQL is relatively old, and compared to other programming languages, has been around for quite some time. That being said, I don't see it disappearing any time soon. SQL is an efficient and logical method for working with databases. Even with newer programs, optimal languages for this form of work will likely always have some basis from SQL; it's probably not going away unless databases do, which certainly won't happen.

    ReplyDelete
  3. Dianna,

    I really enjoyed the portion of your post where you gave the specifics of the type of code that is typically used in SQL. It is important to know what the specific code is in order to fully understand what SQL does and its purpose. I also liked how you related SQL to the present day and how it has evolved since its inception in the 1970s by relating it to smartphones and tablets.

    ReplyDelete
  4. Dianna,
    I had a little coding experience but I was still struggling with languages like Python and HTML. Needless to say SQL is probably going to be even more challenging as it is one of the oldest languages. But like you have mentioned it can transcend the barriers between platforms, and draw data from database. This ability is quite amazing as with the well structured codes we can extract the information exactly what we need. I am sure that I will keep looking into it.

    ReplyDelete
  5. I agree that the coding behind SQL may seem primitive, and this is likely a holdover not only of the age of the language but also of the original use. When it was first invented the amount of data being used in a particular program was not nearly as large as what is used today, and the first uses were likely not web based. Today's use of databases to store so much more information is much more complex and contains many more categories and tables, which is likely why the language seems so cumbersome. The first databases were along the scale of a large Excel sheet, not a set of data which requires a set of servers to hold it as today's do.

    ReplyDelete