HNHacker News
TopNewBestAskShowJobs

westonOG

35 karma · joined June 2, 2023

submissionscomments
westonOG··on Show HN: SQL Simulator – Create Subsetted Databases in Docker or K8s
LOL, thanks for the feedback. I see what you are saying. I need to say what version I've tried it against. I have not tried it against any of the MariaDB variants, so more than likely it won't work with those.
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
In enterprise environments this is pretty common. I've worked at places with over 100 developers and 30 testers. So you have a situation with hundreds if not thousands of databases and then multiple schemas in each database. So imagine trying to manually validate if your script will work on all those databases and against all those schemas. How difficult of a task that is.
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Oh I see. Got it.
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Don't worry I have a thick skin. It's better for people to tell me what they don't like or if there is a better way to do something than to say they like the product when they really don't. The really nifty thing with my program is you can see what the data would look like. I can't tell if your script does that.
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
OK, Thanks for the info. I will keep that in mind.
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Thanks for responding. I apologize for the confusion, but part of that is because I am just learning how to market this product. So, SQL Simulator is a feature of both Ratifier and Kulvert. Ratifier is meant to be a data validation or QA tool. Where as Kulvert is a CI\CD pipeline for SQL Scripts. You would use the SQL Simulator in the Ratifier to test your changes before you check them in. You would use Kulvert to apply your changes to the database if and only if SQL Simulator found no problems with the SQL Script or other logic checks.

I may need to create separate gitbooks for each of the programs so that would reduce the confusion. I hope you will find success with your product.

westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Thanks for the feedback. I use Java to do the static code analysis, C# for the front end and DB connections. One of the biggest issues I've had is trying to explain what it does and how it does it. If I say too much I scare people away. So I am not sure how much information to give at once. As for coding it over a weekend, it's taken me a few years to get it to this point I doubt I could re-write it that quick :-)
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
You are correct. But if someone ran that DML in production it would have the same effect but worse. I am thinking of ways to reduce this issue in the future. I have not settled on a solution just yet.
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Hi, Thanks for you response. Here are my responses to your responses

"tool is closed source" I am open to changing to open source but I do not understand the business model yet.

"tool is windows executable" I created my program with C# and java. I had a sql server dev try to run it but he didn't have java installed on his computer. Apparently they have an intense dislike for java and avoid using programs that need java like the plague. LOL I guess I can't win either way?

"pricing page is 'contact us'" There is no lockout feature of the program that stops working after X days if you don't buy it. Also I am a 1 person startup. I am extremely flexible on pricing. I am not sure what people are willing to pay for it, so it is hard to put a price on it.

westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Out of curiosity, What kind of marketing have you done so far?
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Thank you for your feedback. I added it to my comment. Where else should I add this information?
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
OK, Thank you for the feedback. How much traction have you been able to get for your project so far?
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
How does this work when you need to test your script against multiple databases and multiple schemas? Is this for an enterprise size application?
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Hi, I appreciate the feedback. Which page are you referring to that has stock photos? I am not exactly sure what I need to show people. This program does a lot of batch processing and most of the questions I get are usually related to how does it work.
westonOG··on Show HN: SQL Dry Runs with SQL Simulator
Hi, thanks for responding. This tool automates the tasks you stated in your comment. Instead of having to write specialty code every time you need to test your sqls you can click a button and have the tool set up it up for you. Also what happens if you need to test your SQL against multiple database(ie IUAT/Model Office/Production) and/or multiple schemas? This is just one click in my program.