Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

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

Ensure Compatibility of All Commands with PostgreSQL #12

Closed
getpinga opened this issue Aug 23, 2023 · 1 comment
Closed

Ensure Compatibility of All Commands with PostgreSQL #12

getpinga opened this issue Aug 23, 2023 · 1 comment
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@getpinga
Copy link
Contributor

getpinga commented Aug 23, 2023

We have identified the need to test all commands in Namingo for compatibility with PostgreSQL. This is a crucial step in ensuring that our application functions seamlessly across different database systems, particularly when transitioning from MariaDB to PostgreSQL.

A key area of focus should be the "update" column in the domain table. We suspect that there might be nuances in how PostgreSQL handles data in this column compared to MariaDB. Thorough testing and validation are required to confirm its behavior and ensure data integrity.

Additionally, specific attention must be paid to date calculations. These operations are known to have subtle differences between database systems, and it's essential to ascertain that our date-related functionalities perform consistently across both MariaDB and PostgreSQL.

We are calling for contributors to assist in this testing process. Here’s how you can help:

1. Test Execution: Run existing commands and observe their behavior in a PostgreSQL environment. Pay special attention to data manipulation commands and those involving date calculations.

2. Issue Reporting: If you encounter any discrepancies or errors, please document them with detailed descriptions and steps to reproduce. This information will be invaluable in pinpointing and resolving compatibility issues.

3. Suggestions and Fixes: If you have expertise in PostgreSQL and have suggestions for modifications or fixes to improve compatibility, your input would be highly appreciated. Code snippets, pull requests, or detailed explanations of potential solutions are all welcome.

Your contributions to this effort will play a significant role in enhancing the robustness and flexibility of our system. Thank you in advance for your support and involvement!

@getpinga getpinga added the bug Something isn't working label Aug 23, 2023
@getpinga getpinga self-assigned this Aug 23, 2023
@getpinga getpinga changed the title All commands should be tested for PgSQL compatibility Ensure Compatibility of All Commands with PostgreSQL Dec 7, 2023
@getpinga getpinga added the help wanted Extra attention is needed label Dec 7, 2023
@getpinga
Copy link
Contributor Author

Update: most parts should work with PostgreSQL. Only some date calculaitons can fail, we are gradually replacing them with compatible alternatives.

@getnamingo getnamingo locked and limited conversation to collaborators Feb 19, 2024
@getpinga getpinga converted this issue into discussion #87 Feb 19, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
bug Something isn't working help wanted Extra attention is needed
Projects
Status: v1.1
Development

No branches or pull requests

1 participant