mirror of
https://github.com/PlayEdu/PlayEdu
synced 2025-12-30 07:02:56 +08:00
!13 LDAP优化增强
* cursorrules * fixed: ldap同步的部门记录name记录错误 * 主题色一致 * changelog * admin接入ldap同步数据统计 * ldap同步数据记录接口合并 * fixed: 已同步被禁用用户的DN更新 * 已经同步的LDAP用户被禁止可以继续更新 * 优化代码 * 新增LDAP同步的详细记录 * 新增LDAP禁止用户的数据量统计 * 优化LDAP拉取数据的重复使用 * 优化LDAP同步 * ldap同步记录 * cursor rules
This commit is contained in:
40
.cursor/rules/07-database-structure.mdc
Normal file
40
.cursor/rules/07-database-structure.mdc
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
description:
|
||||
globs:
|
||||
alwaysApply: false
|
||||
---
|
||||
# PlayEdu Database Structure
|
||||
|
||||
This guide outlines the database structure of the PlayEdu application.
|
||||
|
||||
## Database Technology
|
||||
- MySQL database for persistent storage
|
||||
- Redis for caching and session management
|
||||
- MyBatis as the ORM framework
|
||||
|
||||
## Core Tables
|
||||
- **admin_users** - Administrator user accounts
|
||||
- **admin_roles** - Administrator roles for RBAC
|
||||
- **departments** - Organizational departments
|
||||
- **users** - Student/learner accounts
|
||||
- **courses** - Course information
|
||||
- **resources** - Media and document resources
|
||||
- **course_chapters** - Course chapter organization
|
||||
- **course_hour_records** - Learning progress tracking
|
||||
|
||||
## Entity Relationships
|
||||
- Departments have many Users (many-to-many)
|
||||
- Courses have many Chapters (one-to-many)
|
||||
- Courses have many Resources (many-to-many)
|
||||
- Users have progress records for Courses (many-to-many)
|
||||
|
||||
## Database Access
|
||||
- Data access through MyBatis Mappers
|
||||
- [Example Mapper](mdc:playedu-api/playedu-course/src/main/java/xyz/playedu/course/mapper/CourseMapper.java)
|
||||
- XML query definitions in resource XML files
|
||||
- [Example XML](mdc:playedu-api/playedu-course/src/main/resources/mapper/CourseMapper.xml)
|
||||
|
||||
## Data Migration
|
||||
- Managed through SQL scripts
|
||||
- Version controlled database changes
|
||||
- Backup procedures for data safety
|
||||
Reference in New Issue
Block a user