On December 7th, Gitora founder Yalim Gerger will be at the NYOUG Winter Event to talk about version control of PL/SQL using Git. Click here for the full agenda. We hope to see you there!
We are excited to announce the launch of Gitora 7, which includes a groundbreaking addition to our suite of tools: The Gitora PL/SQL Editor The Gitora PL/SQL Editor represents a fresh approach to writing PL/SQL code, drawing on the latest advances in code editors to deliver an unparalleled experience to the PL/SQL community. Packed with modern features that are intuitive and easy to use, this editor represents a significant leap forward in coding in PL/SQL. Let’s take a quick look at some of the features that make the Gitora PL/SQL Editor so remarkable: Beautiful Design The Gitora PL/SQL Editor boasts a beautiful, modern design that makes it easy on the eyes and intuitive to use. With Bootstrap 5 components and Font Awesome icons, you can rest assured that the editor will be both stylish and functional. Dark Mode When you’re working long hours on code, the last thing you want is to strain your eyes. That’s why the Gitora PL/SQL Editor comes with a gorgeous dark mode that is easy on th
With Gitora 6 , developers can work on the same code base (i.e. a package, procedure etc…) in the same database without blocking each other. Many development teams use a single database for development. Many of them use the same database for testing, as well. They achieve this by using different schemas for different purposes. Gitora 6 enables these teams to create Git repos for these schemas and pull updates between them. With Gitora 6, you can even create a different schema for every developer and have them merge their code using Git. Gitora 6 enables you to implement any modern development workflow in a single database. How does Gitora 6 work? Gitora 6 introduces a new repo type called Single Schema Repo (SSR) . As its name suggests an SSR manages database objects from a single schema. The DDL scripts in SSR’s don’t contain the schema prefixes so that Gitora can execute them in other schemas in the same database. This enables developers to work on the same package, procedure, fu
You use a version control system to solve certain problems, to accomplish certain tasks. These are: Keep track of who changes what, when and why. If necessary, use previous versions of the code base for testing, development etc… Move changes between environments faster, with fewer errors during deployment. Improve productivity of the team (i.e. less time coordinating manually and more time developing. For example different developers working on the same parts of the code base simultaneously and merging their changes at a later time, hopefully mostly automatically.). If you are using a version control system but not accomplishing any of the things above, are you really using a version control system? Here is a perfectly reasonable scenario that I’ve seen in the real world. I’ve seen this scenario with teams using Git with SQL Developer, SVN/Git with another Oracle PL/SQL IDE. Invariably, they all end up here: In the DEV database, you make changes to the package PKG_HIRING in the HR sc
Comments