-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create happysql #12
Create happysql #12
Conversation
How mature is HappySQL? It looks like something that's been used in production, but I don't see any tests for the server part. |
Will create issues on the repo :) |
That sounds good, but it doesn't exactly answer my question about maturity. :-) The issue mentions that you plan to document how your company uses HappySQL in production. You can tell me that in a few words here and it will be enough for me. |
FYI @dbohdan, HappySQL has not moved for two years, since the PR was added. I think you're ok to close this with no merge. |
@moul What is the development status of HappySQL? |
As @tamsanh said it before, the repo has not moved for two years HappySQL is used in production since that time and never required any change for now I can't speak about the maturity of our own needs, but the current version of the software is mature enough to cover them To be honest, I don't give a fuck if you close this PR without merging it, my open-source spirit forced me to propose this software on places where other people are happy to discover new alternatives I can understand that you only accept the most used/favorited/still-active ones 👍 |
It speaks to HappySQL's quality that it has been running in production this whole time. However, I would still rather not add software without tests. Since the project isn't abandoned, I don't see a reason to close the PR. I will keep it open in case more development happens and tests are added. |
The repository has been archived. Closing. Please resubmit if there is ongoing development in some other repository. |
No description provided.