I ran across a Twitter post today that asked what feature they’d remove from FileMaker Pro. I don’t use FileMaker (not in many, many years at least), but I thought it was a very good question.
It’s a good question in regards to Real Studio too as it makes you think about what you don’t use. I’ve asked the question before on what’s the one thing you need above all else in Real Studio. But removing something is a much harder question. So it should probably be something that’s not very good, or makes things worse, or something made irrelevant by 3rd party tools.
After thinking about it for just a few seconds I came up with the one thing that I never use in Real Studio: The Database Editor. For me, it’s the one thing that is worse than useless since it makes the job of managing your databases harder. I mean,it’s just not very good, in my opinion. Based on my experience answering questions in the Real Software forums it’s not an uncommon experience.
In reality, the database editor experience is much like any generic tool: it just doesn’t have the features that match up well to tools built for the specific database. If you want a good SQLite tool there are some awesome commercial versions available. Heck, there is a freeware version that works inside of FireFox that’s better than the DB editor, IMO. The same goes with MySQL, PostgreSQL, Oracle and any other database that RS supports.
I’m a big fan of Navicat as they have versions of each of the aforementioned databases. Granted, Navicat has a generic user interface and it’s a Java app (I think) but it’s the only thing that Navicat does (database admin tools). It’s interface is consistent across all of their versions so it’s no big deal to move from the SQLite version to the PostgreSQL or the MySQL version.
If the Database Editor was removed from Real Studio would anyone really notice? What would you remove from Real Studio if you had the chance?