After using DB1 a fair amount I think it brings a lot of value to the daily workflow of someone that uses databases a fair amount, and uses Sublime Text. In addition to that, I have plans to support 3 or 4[1] more databases soon and add a fair amount of complicated features.
That said though, if I hear from a fair amount of people that the price point is too high then I may consider lowering it.
[0] https://eggerapps.at/postico/ [1] https://github.com/sequoiastudios/DB1/issues
For example, if your price per hour is $20 and this tool saves you 1.5 hours of time in your lifetime, it would make the business case. Or, if your price per hour is $5 and it saves you 6 hours in your lifetime it also would make the business case.
However, it would be a bad investment if your price per hour is $5 and it only saves you 5 hours in your lifetime.
In the grand scheme of things, I think it all depends on how much you interact with a db. If you just run an odd command here and there, $30 may seem like a lot. If you work with databases for an hour or more a day, this could be a huge time-saver.
How is it possible anyway? Queries in source files almost always cannot be executed as such, because of placeholders/parameters. Or what am I missing?
I am interested to see how "version 2" of this pans out.
For the record, workbench is not the end-all. It is quite clunky.