[StoneDB] Remove implementation#963
Conversation
|
I'm unsure if StoneDB is still actively maintained. After joining their Slack community one year ago, I noticed there's been no activity or messages this year. Additionally, their commit history shows that updates haven't been made in quite some time. |
Sorry, something went wrong.
|
alright, are you ok with us removing it for now? @Zhenglin-Li |
Sorry, something went wrong.
4e42925 to
42af319
Compare
August 23, 2024 03:06
oh yeah, let's remove |
Sorry, something went wrong.
|
Sounds good, we can always re-add by reverting the PR in case development continues. @malwaregarry, perhaps we could have a table in the |
Sorry, something went wrong.
|
ok sure, do you want the |
Sorry, something went wrong.
|
Hmm, a separate one would be okay. I guess we could then also reference the removed NoSQL databases (#915). |
Sorry, something went wrong.
Removing StoneDB from the codebase since the implementation is broken and StoneDB seems to be unmaintained at the moment.
This is part of efforts to improve SQLancer's architecture and codebase in general. If it is being used, we can revert the PR.
@Zhenglin-Li since you worked on this implementation. Do you know whether the StoneDB is still working on the database?