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.

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

Test feature parity between PSQL and SQLite DB backends #6621

Open
Tracked by #6435
GeigerJ2 opened this issue Nov 20, 2024 · 0 comments
Open
Tracked by #6435

Test feature parity between PSQL and SQLite DB backends #6621

GeigerJ2 opened this issue Nov 20, 2024 · 0 comments

Comments

@GeigerJ2
Copy link
Contributor

Currently, there are various tests that are marked with requires_psql, e.g., here:

@pytest.mark.requires_psql
def test_as_sql(self):
"""Test ``qb.as_sql(inline=False)`` returns the correct string."""
qb = orm.QueryBuilder()
qb.append(orm.Node, project=['uuid'], filters={'extras.tag4': 'appl_pecoal'})
self.regress_str(qb.as_sql(inline=False))

We should check which of those tests are missing for SQLite (such as def test_as_sql linked above that is, due to the mark, only ever run for PSQL), which ones should actually work for both, and which ones truly require PSQL (e.g., PSQL-backend specific ones, of course), to achieve testing feature parity between the different SQL backends.

Pinging @danielhollas and @rabbull.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant