feat: impl dal transaction

[killagu]

Checklist

• npm test passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

Description of change

Summary by CodeRabbit

• New Features

  • Enhanced transaction management with the introduction of new lifecycle hooks and classes to ensure proper handling and isolation across various operations.
  • Added a new development dependency to support aspect-oriented programming techniques for transaction advice.

• Documentation

  • Updated configuration files and added new SQL scripts to define database structures and queries.

• Tests

  • Introduced comprehensive test cases for transaction management, covering various scenarios including successful and failed transactions.
  • Added a new test suite for dal transaction runner with assertions for different transaction scenarios.

[coderabbitai]

Walkthrough

The updates involve expanding the testing suite for the dal transaction runner within the index.test.ts file. This new test suite covers various transaction scenarios, enhancing the testing coverage for this specific component.

Changes

Files	Changes
standalone/standalone/test/index.test.ts	Added a new test suite for dal transaction runner with assertions for different transaction scenarios.

🐰🌱
A test suite blooms in the code's domain,
Validating transactions with precision, not in vain.
Assertions dance like fireflies at night,
Ensuring each transaction's path is bright.
Cheers to the testers, diligent and keen,
In the realm of tests, quality is seen.
🌟🐇

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 02a50e7 and 72f0e39.

Files selected for processing (1)

• standalone/standalone/test/index.test.ts (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• standalone/standalone/test/index.test.ts

---

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>.
  • 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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[fengmk2]

+1

[coderabbitai]

Actionable comments posted: 5

[killagu]

• @eggjs/ajv-decorator@3.38.0
• @eggjs/aop-decorator@3.38.0
• @eggjs/controller-decorator@3.38.0
• @eggjs/core-decorator@3.38.0
• @eggjs/dal-decorator@3.38.0
• @eggjs/dal-runtime@3.38.0
• @eggjs/egg-module-common@3.38.0
• @eggjs/eventbus-decorator@3.38.0
• @eggjs/standalone-decorator@3.38.0
• @eggjs/tegg@3.38.0
• @eggjs/tegg-ajv-plugin@3.38.0
• @eggjs/tegg-aop-plugin@3.38.0
• @eggjs/tegg-aop-runtime@3.38.0
• @eggjs/tegg-background-task@3.38.0
• @eggjs/tegg-common-util@3.38.0
• @eggjs/tegg-config@3.38.0
• @eggjs/tegg-controller-plugin@3.38.0
• @eggjs/tegg-dal-plugin@3.38.0
• @eggjs/tegg-dynamic-inject@3.38.0
• @eggjs/tegg-dynamic-inject-runtime@3.38.0
• @eggjs/tegg-eventbus-plugin@3.38.0
• @eggjs/tegg-eventbus-runtime@3.38.0
• @eggjs/tegg-lifecycle@3.38.0
• @eggjs/tegg-loader@3.38.0
• @eggjs/tegg-metadata@3.38.0
• @eggjs/tegg-orm-decorator@3.38.0
• @eggjs/tegg-orm-plugin@3.38.0
• @eggjs/tegg-plugin@3.38.0
• @eggjs/tegg-runtime@3.38.0
• @eggjs/tegg-schedule-decorator@3.38.0
• @eggjs/tegg-schedule-plugin@3.38.0
• @eggjs/tegg-standalone@3.38.0
• @eggjs/tegg-transaction-decorator@3.38.0
• @eggjs/tegg-types@3.38.0