langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 10:05:47 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #199] [MERGED] update database #704

New Issue
Closed
opened 2026-02-22 17:36:30 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 17:36:30 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/199
Author: @hjlarry
Created: 3/21/2025
Status: ✅ Merged
Merged: 3/23/2025
Merged by: @crazywoola

Base: main ← Head: p0

📝 Commits (1)

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

📝 hjlarry/dify-plugin-database.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Submission Type

  • New plugin submission
  • Version update for existing plugin

2. Description

0.0.4

  • support sqlserver, oracle connection
  • change db_url to a llm format, so that user can use a environment variable of workflow to set the database uri
  • fix in a agent app, sql_execute tool only response the first result
  • migrate the table schema info of the text2sql tool to a user prompt, to prevent system prompt too long then response nothing

3. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

4. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details

5. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/199 **Author:** [@hjlarry](https://github.com/hjlarry) **Created:** 3/21/2025 **Status:** ✅ Merged **Merged:** 3/23/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `p0` --- ### 📝 Commits (1) - [`bae57ca`](https://github.com/langgenius/dify-plugins/commit/bae57cab84d2a741778c162db01a3214b25bb88e) update database ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `hjlarry/dify-plugin-database.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Submission Type - [ ] New plugin submission - [x] Version update for existing plugin ## 2. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> #### 0.0.4 - support sqlserver, oracle connection - change `db_url` to a llm format, so that user can use a environment variable of workflow to set the database uri - fix in a agent app, `sql_execute` tool only response the first result - migrate the table schema info of the text2sql tool to a user prompt, to prevent system prompt too long then response nothing ## 3. Checklist - [ ] I have read and followed the Publish to Dify Marketplace guidelines - [ ] I have read and comply with the Plugin Developer Agreement - [ ] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [ ] I confirm my plugin has been thoroughly tested for completeness and functionality - [ ] My plugin brings new value to Dify ## 4. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [ ] Step-by-step setup instructions - [ ] Detailed usage instructions - [ ] All required APIs and credentials are clearly listed - [ ] Connection requirements and configuration details ## 5. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection <!-- Does your plugin collect any user personal data? If yes, please list what types of user personal data are being collected according to the Plugin Privacy Protection Guidelines (for example: Email address, IP address, Age, etc) --> ### Privacy Policy - [ ] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 17:36:30 -05:00
yindo closed this issue 2026-02-22 17:36:34 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#704
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?