To be honest the pricing was something I really struggled with. I finally ended up settling on that price as it was similar[0] to some of the other database clients on the market, and similar to the pricing of other Sublime Text plugins.

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

Pricing is important. You might make 100000x the sales of a 0.99 app than you do of a 10.00 app. I closed the tab when I saw the price you'd set, and just forgot about the subject. Sublime integration just isn't worth that much money. Yet.

I think this do almost the same and it is free [SQLExec](http://lubriciousdevelopers.github.io/projects/sublime-sql-e...)

I agree. I feel its worth the $9 price point too. $29? No way. Sublime Integration isn't worth $20 when I can just alt+tab. There are a lot of free apps that provide a ton more db functionality.

But if you are alt-tabbing, you no longer have the full suite of Sublime Text tools to work with. You don't have multiple cursors, and you can't use goto file, you don't get nice syntax highlighting, you can't select and execute SQL embedded in other source code files.

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.

I don't know that I'd save that much time switching back and forth between sublime and workbench is my typical workflow. I gain a lot from the multiple cursors when building multiple insert/delete statements...but not sure what other situations where I could leverage this plugin to save time [with sql].

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.

>you can't select and execute SQL embedded in other source code files..

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?

Since it is convenience/time save tool, price point suitability will depend largely in your price per hour.

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.