含多表CRUD及check方法的类：属于Repository还是DAO？

Great question! Let’s break this down clearly by first defining the core purpose of each pattern, then mapping it to your class’s methods.

Core Differences Between DAO and Repository #

• DAO (Data Access Object)：This pattern is all about handling the raw, database-specific details of data interaction. DAOs act as a direct bridge between your app and the database, with methods tied directly to SQL operations—think joins, bulk inserts, targeted updates, etc. They don’t hide these implementation details; they exist to execute them reliably.
• Repository: This pattern wraps data access in domain-centric, business-focused abstractions. Instead of exposing multi-table JOINs or raw inserts, repositories work with your app’s core entities (like User or Order) and offer methods that align with business needs (e.g., getActiveUsersWithRecentOrders() instead of a raw SELECT with joins). They often use DAOs under the hood but shield the rest of the app from database-specific logic.

Mapping Your Class to the Patterns #

Looking at your class’s methods:

• find: Uses multi-table JOINs in a SELECT statement (direct database operation detail)
• add: Handles multi-table inserts (specific database write logic)
• update: Manages multi-table updates (database-specific modification)
• delete: Executes multi-table deletes (direct database deletion)
• check: Runs multiple JOINed SELECTs for validation (database-focused check)

Every method here is rooted in direct, database-specific actions—you’re working with SQL constructs and low-level database interactions, not abstracting these into business-aligned entity behaviors. There’s no layer of abstraction that hides the database details behind domain-focused operations.

Final Verdict #

This class is absolutely a DAO.

内容的提问来源于stack exchange，提问作者Combo