Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Database] Rearrange internal machinery to accommodate NoSQL databases #256

Open
c410-f3r opened this issue Oct 29, 2024 · 0 comments
Open

[Database] Rearrange internal machinery to accommodate NoSQL databases #256

c410-f3r opened this issue Oct 29, 2024 · 0 comments
Assignees
@c410-f3r
Labels
D-hard Difficult - Hard F-database Feature - Database T-new-feature Type - New feature

Comments

@c410-f3r
Copy link
Owner

PostgreSQL is the only supported database and that is basically the reason why the traits are highly coupled to traditional RDBMS operations.

To also accommodate NoSQL databases it is necessary to first create an implementation (Redis? Memcached?) and then modify the internal structures to share as many definitions as possible.
@c410-f3r c410-f3r added T-new-feature Type - New feature F-database Feature - Database D-hard Difficult - Hard labels Oct 29, 2024
@c410-f3r c410-f3r changed the title [Database] Re-arrange mechanery to accomodate NoSQL databases [Database] Rearrange internal machinery to accommodate NoSQL databases Oct 29, 2024
@c410-f3r c410-f3r self-assigned this Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@c410-f3r c410-f3r

Labels
D-hard Difficult - Hard F-database Feature - Database T-new-feature Type - New feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@c410-f3r