- π Feature: Add Support for Redis as a Caching Layer
Description π:
Currently, DBDuck supports 6 databases (PostgreSQL, MySQL, SQLite, MSSQL, MongoDB, Neo4j) ποΈ. To improve performance for high-traffic applications β‘, we should implement a caching layer using Redis π΄.
Tasks β
:
Create a RedisManager within the core logic π§ .
Implement get_cache and set_cache methods in the UDOM abstraction layer π.
Allow users to toggle caching in the configuration βοΈ.
Labels π·οΈ: enhancement β¨, help wanted π€
- π‘οΈ Security: Expand Automated Security Scanning (Bandit & Safety)
Description π:
We previously resolved 28 SQL injection vulnerabilities in v0.3.0 ππ¨. To maintain this standard π‘οΈ, we need to integrate more robust security tools into our CI/CD pipeline βοΈπ€.
Tasks β
:
Add Safety check to the GitHub Actions workflow to scan for insecure dependencies ππ¦.
Configure Bandit to fail the build if any High-severity security issue is detected in new PRs π«β.
Update documentation with a "Security Best Practices" section for users ππ.
Labels π·οΈ: security π, CI/CD π
- π Documentation: Add "Getting Started" Video and Interactive Examples
Description π:
The documentation site (dbduck.org.in) is live with 71 components π, but we can improve the onboarding experience for new Python developers ππ.
Tasks β
:
Create a 2-minute "Quick Start" video guide π₯β±οΈ.
Add an interactive "Try it in Browser" (using Pyodide or similar) to test UDOM logic without installation π»β¨.
Translate core documentation into multiple languages to increase global reach ππ£οΈ.
Labels π·οΈ: documentation π, good first issue π
- π οΈ Feature: Implement Migration Tooling (CLI)
Description π:
DBDuck provides a single unified API across databases ΩΎΩΫ, but users need an easy way to migrate schemas between different database types (e.g., SQLite to PostgreSQL) automatically πποΈ.
Tasks β
:
Develop a CLI command: dbduck migrate --from sqlite --to postgres π»β¨οΈ.
Ensure data types are mapped correctly across SQL and NoSQL dialects πΊοΈπ.
Add a --dry-run flag to validate migrations before execution π§ͺπ.
Labels π·οΈ: feature-request π‘, CLI π₯οΈ
Description π:
Currently, DBDuck supports 6 databases (PostgreSQL, MySQL, SQLite, MSSQL, MongoDB, Neo4j) ποΈ. To improve performance for high-traffic applications β‘, we should implement a caching layer using Redis π΄.
Tasks β :
Create a RedisManager within the core logic π§ .
Implement get_cache and set_cache methods in the UDOM abstraction layer π.
Allow users to toggle caching in the configuration βοΈ.
Labels π·οΈ: enhancement β¨, help wanted π€
Description π:
We previously resolved 28 SQL injection vulnerabilities in v0.3.0 ππ¨. To maintain this standard π‘οΈ, we need to integrate more robust security tools into our CI/CD pipeline βοΈπ€.
Tasks β :
Add Safety check to the GitHub Actions workflow to scan for insecure dependencies ππ¦.
Configure Bandit to fail the build if any High-severity security issue is detected in new PRs π«β.
Update documentation with a "Security Best Practices" section for users ππ.
Labels π·οΈ: security π, CI/CD π
Description π:
The documentation site (dbduck.org.in) is live with 71 components π, but we can improve the onboarding experience for new Python developers ππ.
Tasks β :
Create a 2-minute "Quick Start" video guide π₯β±οΈ.
Add an interactive "Try it in Browser" (using Pyodide or similar) to test UDOM logic without installation π»β¨.
Translate core documentation into multiple languages to increase global reach ππ£οΈ.
Labels π·οΈ: documentation π, good first issue π
Description π:
DBDuck provides a single unified API across databases ΩΎΩΫ, but users need an easy way to migrate schemas between different database types (e.g., SQLite to PostgreSQL) automatically πποΈ.
Tasks β :
Develop a CLI command: dbduck migrate --from sqlite --to postgres π»β¨οΈ.
Ensure data types are mapped correctly across SQL and NoSQL dialects πΊοΈπ.
Add a --dry-run flag to validate migrations before execution π§ͺπ.
Labels π·οΈ: feature-request π‘, CLI π₯οΈ