Summary and Questions
So far, in this database class we have learned how to not only create database, but also how to manage them. One of the coolest concepts I came across was using Views. I can very much see myself using this ability this ability in SQL when administrating my own databases on my personal and profesional projects. On the creation side of things we also learned how different tables interact without each other through foreign keys. The ability to be able to declare a table's column field as needing a value through NOT NULL pretty much, in my opinion, is one of the pillars of strengths SQL gives us. On top of this, when we learned about the ability to create a union through UNION in SQL I saw the great possibilities there. In all honestly though, SQL is a very simple language, the complexity rests with the schemas. The ability that we have learned in designed our own diagrams arguably is more important than the SQL language itself. The diagrams really show us the design and idea that went behind and entire database.
That said, there is three questions that I have that have not been answered in the class so far:
- How exactly do other programming languages, fore example JavaScript interact with an SQL database?
- Are most database designes in the real world built up of just a few tables, or are most databases extremely complex?
- Is there a specific code style that is preferred when naming things in SQL databases (e.g. snake, camel)?
No comments:
Post a Comment