Skip to content

Do programmer have a fear of commitment? Database commits that is

Every now and then you’ll see my throw up my hands in frustration and mutter something “why aren’t you showing up!” It’s a common scenario, you insert some data directly into the database, command+tab over to your favorite web browser with your application already loaded up, hit refresh…record doesn’t show up. Where is it!!! Well, I never clicked that little green checkmark (in SQLDeveloper at least). In database GUI land it looks present, but in the real world, nada.

Why don’t I just turn autocommit on? Because, I’ll admit it, I make mistakes. One of the unfortunate side effects of running dual monitors is you some times you think you’re typing in one application, but you’re really not, you never gave it focus. With autocommit on, this could potentially spell messed up data. What about rolling it back? I don’t always know what application I was typing in either, some times it’s just a mystery where that “logger.debug()” I just typed actually went. This at least prevents me from inadvertently causing a bigger problem than the inconvenience of having to click commit.

Related posts:

  1. Hit a snag with Netbeans, Maven, and testing utils.

Post a Comment

Your email is never published nor shared.