SQL (pronounced S-Q-L or Sequel) is a query based language used for storing databases, and organizing or manipulating data. I did not have any previous experience with SQL prior to this internship, so before I started I used the app SoloLearn to know the basics and used W3 Schools to learn something quickly, as well as Pluralsight to gather a bigger picture of potential applications of SQL. Although I did not do a lot of development in SQL it was still vital to know how to search through databases in order to correct test information being processed in the Interface applications. Below are some of the developments I worked on.
One of the first SQL related JIRAs I worked on added a default safety rating to one of the apps. Reported by QA, the default rating was "S" for some, meaning "Satisfactory," when they thought it should be "N." But, as a developer, we decided to make it the users choice on what the default would be, so we added the row that would set it, but also allowed the user to change the default value of "N."
Another SQL issue I worked on was fuel code mapping to the wrong fuel types. At first, it seemed like a simple fix, but the fuel types needed to be consistent with types that could actually trigger the correct prices of the fuel. For example, the type of fuel needed to be Ultra Low Sulfur Diesel, but with the correct correlation to gas, it needed to be mapped as just DSL (diesel) or else it would not have registered as a valid fuel type. Additionally, some SQL components that reside in the old coding framework called PowerBuilder are still used by some clients. So, in addition to changing the mapping in the new .NET solution, I also had to receive deeper clearance to commit changes to PowerBuilder.