It is generally accepted that you should always use proper version control when developing software. Why wouldn't you do the same with your database changes? It's even more important as part of a DevOps continuous integration strategy. Evolving your database schema using SQL scripts seems easy at the start but quickly becomes a nightmare as your application grows more complex. How do you track which scripts have been run? How do you rollback changes? Can you conditionally run certain changes for different environments? In this session Blaine Carter will discuss using a schema...
Blaine Carter
Developer Advocate for Open Source
Oracle
For most of his career, Blaine Carter has used Oracle tools to build applications—mostly SQL and PL/SQL. Lately he's been exploring open source projects, and he has used quite a few languages and liked almost all of them. His combined experience with Oracle Database and open source led him to a brand-new position at Oracle: Oracle Developer Advocate for Open Source. He helps database developers improve their workflow using open source tools and promotes the use of open source inside and outside of Oracle.