Implement GraphQL comparison: PostgreSQL+Hasura vs Doublets+GQL #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π― Summary
This PR implements the first version of GraphQL comparison between PostgreSQL+Hasura and Doublets+GQL, as requested in issue #1.
π Implementation Details
β Core Components
π GraphQL Operations Benchmarked
Based on the existing benchmark operations, implements GraphQL equivalents:
Mutations (Write Operations):
createPointLink- Creates point links (id = source = target)createLink- Creates regular linksupdateLink- Updates existing linksdeleteLink- Deletes links by IDQueries (Read Operations):
allLinks- Get all links ([*, *, *]constraint)linkById- Get by ID ([id, *, *]constraint)concreteLinks- Get by source+target ([*, source, target]constraint)outgoingLinks- Get outgoing ([*, source, *]constraint)incomingLinks- Get incoming ([*, *, target]constraint)π Usage
Local Development:
GitHub Actions:
Automatically runs on push/PR and publishes results to
gh-pagesbranch.π Results
The implementation generates:
π§ Technical Details
π Closes
Fixes #1
π€ Generated with Claude Code