linksplatform / linksplatform/Data.Doublets.Sql
Implement SQL server for Doublets
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
3000 RUB reward can be claimed from [github.com/kalinochkind](http://github.com/kalinochkind) by anyone who completes this task.
It should be possible to insert, update and delete links via SQL mutations.
Furthermore, it should be also possible to search links using any of existing links' IDs, or just get a complete list of links from links storage.
All SQL standard types and user defined (custom) tables creation should be supported as well.
Server, parser and planer part can be implemented using [calcite.apache.org](https://calcite.apache.org) (or any other library/framework with similar number of features).
Access to doublets can be implemented via Java to C# bridge (https://github.com/jni4net/jni4net/ or https://www.javonet.com/pricing/). If that is not possible, Doublets can be accessed via [Gql Server](https://github.com/linksplatform/Data.Doublets.Gql).
All features of SQL standard should be supported to be executed on the virtual links table and custom tables.
[calcite.apache.org](https://calcite.apache.org) is not the only solution that can be used.
The goal is to create a fully featured SQL interface (server + library) to Doublets and custom virtual tables using any language and a set of libraries/tools.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by evaluating the required server, parser, planner, and links-storage behavior against Apache Calcite and the suggested Gql Server or Java-to-C# bridge. Done means supporting SQL mutations, link searches and listing, standard types, custom tables, and the stated SQL features through both the server and library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, java, sql
- Domain
- backend-api-design, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100