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

(DAL) Support multi pgs connection #1780

Closed
wants to merge 2 commits into from

Conversation

nick-bisonai
Copy link
Collaborator

@nick-bisonai nick-bisonai commented Jul 10, 2024

Description

DAL will refer to node db to get config id and otherwise, use its own db having different db connection url.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.

Deployment

  • Should publish npm package
  • Should publish Docker image

@nick-bisonai nick-bisonai self-assigned this Jul 10, 2024
@nick-bisonai nick-bisonai requested a review from a team as a code owner July 10, 2024 10:03
Copy link
Contributor

coderabbitai bot commented Jul 10, 2024

Walkthrough

Walkthrough

This update involves renaming and restructuring components within the dal package. The utils package is renamed to initializer, and new functionalities for interacting with PostgreSQL databases are introduced in the multipgs package. The changes also include adjustments to the test files to reflect these updates and add new test functions for the multipgs package.

Changes

File Path Change Summary
node/pkg/dal/app.go Updated import path from "utils" to "initializer", and modified Setup function call.
node/pkg/dal/tests/main_test.go Updated import path from "utils" to "initializer", and modified Setup function call.
node/pkg/dal/tests/multipgs_test.go Added new test functions for multipgs package functionalities including database and queries.
node/pkg/dal/utils/initializer/... Renamed package from utils to initializer.
node/pkg/dal/utils/multipgs/multipgs.go Introduced new methods for managing PostgreSQL connections and executing queries.

Poem

In the world of code and bytes,
Changes come with dazzling lights,
'Initializer' takes its place,
While 'multipgs' quickens the chase.
PostgreSQL now feels the care,
As queries fly through summer air.
🎉🐰✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0912c0b and bf1e185.

Files selected for processing (5)
  • node/pkg/dal/app.go (1 hunks)
  • node/pkg/dal/tests/main_test.go (2 hunks)
  • node/pkg/dal/tests/multipgs_test.go (1 hunks)
  • node/pkg/dal/utils/initializer/initializer.go (1 hunks)
  • node/pkg/dal/utils/multipgs/multipgs.go (1 hunks)
Files skipped from review due to trivial changes (1)
  • node/pkg/dal/utils/initializer/initializer.go
Additional comments not posted (14)
node/pkg/dal/app.go (1)

8-8: LGTM! Import path update and function call adjustment.

The import path for utils has been correctly updated to initializer, and the function call has been adjusted accordingly.

Also applies to: 16-16

node/pkg/dal/utils/multipgs/multipgs.go (8)

19-38: LGTM! Ensure connection string retrieval is correct.

The function correctly handles the creation and retrieval of PostgreSQL database connections. Ensure the loadPgsqlConnectionString function correctly retrieves the connection string.


40-46: LGTM! Close all database connections.

The function correctly iterates over the dbInstances map and closes each PostgreSQL database connection.


48-50: LGTM! Retrieve connection string from secrets.

The function correctly retrieves the PostgreSQL connection string from secrets.


52-54: LGTM! Establish PostgreSQL connection.

The function correctly establishes a connection to PostgreSQL using the provided connection string and handles errors.


56-58: LGTM! Execute PostgreSQL query.

The function correctly executes a query on the PostgreSQL database using the provided connection pool and query string.


60-73: LGTM! Ensure query execution is correct.

The function correctly handles database connections, executes the query, and logs errors. Ensure the query function correctly executes the query.


75-95: LGTM! Ensure result mapping is correct.

The function correctly handles database connections, executes the query, and maps the result to the expected type. Ensure the pgx.CollectOneRow function correctly maps the result.


97-117: LGTM! Ensure result mapping is correct.

The function correctly handles database connections, executes the query, and maps the results to the expected types. Ensure the pgx.CollectRows function correctly maps the results.

node/pkg/dal/tests/main_test.go (1)

17-17: LGTM! Import path update and function call adjustment.

The import path for utils has been correctly updated to initializer, and the function call has been adjusted accordingly.

Also applies to: 85-85

node/pkg/dal/tests/multipgs_test.go (4)

10-24: LGTM! Test valid and invalid database connections.

The test function correctly validates the creation of a new database with both valid and invalid connection strings and checks for expected errors.


26-64: LGTM! Test query execution without result and cleanup.

The test function correctly handles database connections, executes the query, and checks for expected errors. The cleanup of temporary resources is handled properly.


66-106: LGTM! Test query execution with single row result and cleanup.

The test function correctly handles database connections, executes the query, and maps the result to the expected type. The cleanup of temporary resources is handled properly.


108-148: LGTM! Test query execution with multiple row results and cleanup.

The test function correctly handles database connections, executes the query, and maps the results to the expected types. The cleanup of temporary resources is handled properly.

@nick-bisonai nick-bisonai marked this pull request as draft July 11, 2024 01:45
@nick-bisonai
Copy link
Collaborator Author

will close this pr since decided to take different approach

@nick-bisonai nick-bisonai deleted the feat/support-multi-pgs-conn branch July 11, 2024 03:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant