Is your feature request related to a problem? Please describe.
Not really a problem other than the solution, in my opinion, is more advanced than the current Studio.
Describe the solution you'd like
Would you consider using https://github.com/julianpaulozzi/LiteDbExplorer as the official LiteDB Studio?
LiteDbExplorer is the best tool for LiteDB, ever. But, current version works to v4 only. New v5 works with SQL syntax to query, insert, update, delete or execute any other commands. I will talk with @julianpaulozzi about his plan with LiteDbExplorer
Thank you for enjoying the LiteDbExplorer project. It took many hours of work to considerably evolve the original project.
Any contribution and/or suggestion is welcome, you can submit suggestions by creating an issue on Github.
Yes, I intend to support version 5, I would just like to do it in the same executable and project.
Follow Enchancement Request: V5 Support.
SQL to query is not a problem, there is already an abstraction and composition layer capable of handling this with minor adjustments.
I did a little test using the 2 assemblies together using the AppDomain and CodeBase with the extern alias with initial success.
The challenge now would be not to use the concrete references to BsonValue, BsonType, BsonDocument, BsonArray and ObjectId (almost equal shape in different assemblies) and made some cherry pick versions futures.
HI and thanks for the reply! I suppose that v4 will be out of support soon, and therefore even if LiteDbExplorer support only v5 would be ok. BUt that's, of course, is up to you :)
Also because v5 has an option to upgrade a v4 db to v5.
Anyway I hope v5 support for LiteDbExplorer will be available soon :)
Keep up the goo job!
Most helpful comment
Thank you for enjoying the LiteDbExplorer project. It took many hours of work to considerably evolve the original project.
Any contribution and/or suggestion is welcome, you can submit suggestions by creating an issue on Github.
Yes, I intend to support version 5, I would just like to do it in the same executable and project.
Follow Enchancement Request: V5 Support.
SQL to query is not a problem, there is already an abstraction and composition layer capable of handling this with minor adjustments.
I did a little test using the 2 assemblies together using the
AppDomainandCodeBasewith theextern aliaswith initial success.The challenge now would be not to use the concrete references to BsonValue, BsonType, BsonDocument, BsonArray and ObjectId (almost equal shape in different assemblies) and made some cherry pick versions futures.