Code of Our Lives

  AI is real and it is here. Its implications for knowledge workers will be enormous, including you. There is no escaping AI in our line of work. Therefore, while building the new version of   Gitora PL/SQL Editor , I’ve fully embraced it. The last few months have been the most interesting, rewarding and productive period of my professional life. I’ve practically stopped using Google search and StackOverflow, two websites I’d consider essential to my work just a few months ago. I’ve coded the Gitora PL/SQL debugger virtually without reading a single line of documentation about how to build debuggers in Java or the specifics of how to build a Java debugger for PL/SQL. I am not even sure if there is any documentation available about building a PL/SQL debugger on the Internet. I just talked about these topics with ChatGPT and analyzed, used the code snippets it produced. All CSS and almost all of the run-of-the-mill code I needed to write for the debugger and the Gitora AI Assistant for S

Introducing the Gitora AI Assistant: Write, debug and explain SQL and PL/SQL with the help of AI.     Gitora AI Assistant knows about your tables, their structure and their relationships so that it can give relevant answers. To learn more and download click at this link.

Introducing Gitora PL/SQL AI Assistant. It suggests PL/SQL code in real-time right from the Gitora Editor. This was one of the MOST INTERESTING features I've ever worked on. The first iteration is a small step in the right direction. But the possibilities are ENDLESS. I'd truly appreciate it if you could try it out and provide feedback so that I can improve it. Ideas to where to apply AI next are most welcome. You can download the editor from this link: https://www.gitora.com/plsql_editor.html

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