fix: data write serialization error

[omer-topal]

Summary by CodeRabbit

• New Features
  • Updated API version to v1.3.0, indicating potential new features and improvements.
• Refactor
  • Enhanced backend processes to improve data consistency and reliability during concurrent operations.
  • Streamlined the management of record relationships for smoother conflict resolution.

[coderabbitai]

Walkthrough

This pull request updates the database writing logic by switching the transaction isolation level from pgx.ReadCommitted to pgx.Serializable. It removes the pre-insert relationship batch update calls from both the write and runOperation methods, streamlining the process to perform direct batch inserts. The batch insertion logic now includes an ON CONFLICT clause to prevent duplicate entries when a unique constraint is violated. Additionally, the API version is updated to "v1.3.0" across multiple documentation files. No changes were made to any exported or public entities.

Changes

File(s)	Change Summary
internal/storage/.../dataWriter.go	- Changed transaction isolation level to pgx.Serializable - Removed calls to batchUpdateRelationships in write and runOperation methods - Updated batchInsertRelationships to include an ON CONFLICT clause
docs/api-reference/.../apidocs.swagger.json	- Updated API version from "v1.2.9" to "v1.3.0"
docs/api-reference/openapiv2/.../apidocs.swagger.json	- Updated API version from "v1.2.9" to "v1.3.0"
internal/info.go	- Updated Version constant from "v1.2.9" to "v1.3.0"
proto/base/v1/.../openapi.proto	- Updated version from "v1.2.9" to "v1.3.0"

Sequence Diagram(s)

sequenceDiagram
    participant App as Application
    participant DW as DataWriter
    participant DB as Database

    App->>DW: Call write operation
    DW->>DB: Begin transaction (Serializable)
    Note right of DW: Skips batch update for relationships
    DW->>DB: Execute batch insert with ON CONFLICT handling
    DB-->>DW: Send insert acknowledgment
    DW->>DB: Commit transaction
    DW-->>App: Return result

Loading

Possibly related PRs

• fix(internal): update transaction isolation level to ReadCommitted #2000: Involved similar transaction isolation modifications but in the opposite direction, directly relating to changes in transaction options.
• feat: update version to v1.2.6 in multiple API reference files. #1910: Related to version updates in API documentation, indicating a progression in versioning alongside this PR.

Poem

I'm a bunny, hopping through the code so bright,
Steering transactions with a serial might.
Skipping old routines, new paths in sight,
Inserting with care, avoiding conflict's bite.
Celebrating changes with a joyful hop, day and night! 🐇
Happy coding from your furry friend!

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a47a8a and b517294.

⛔ Files ignored due to path filters (1)

• pkg/pb/base/v1/openapi.pb.go is excluded by !**/*.pb.go

📒 Files selected for processing (4)

• docs/api-reference/apidocs.swagger.json (1 hunks)
• docs/api-reference/openapiv2/apidocs.swagger.json (1 hunks)
• internal/info.go (1 hunks)
• proto/base/v1/openapi.proto (1 hunks)

✅ Files skipped from review due to trivial changes (4)

• internal/info.go
• proto/base/v1/openapi.proto
• docs/api-reference/openapiv2/apidocs.swagger.json
• docs/api-reference/apidocs.swagger.json

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Test with Coverage
• GitHub Check: Analyze (go)
• GitHub Check: Test with Coverage

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.