Update README.md
This commit is contained in:
@@ -154,6 +154,12 @@ Requirements:
|
||||
* A user can have multiple orders.
|
||||
* An order can contain multiple items.
|
||||
|
||||
Note:
|
||||
Order is a reserved SQL keyword in many database systems.
|
||||
Choose an appropriate table name such as `orders` if needed.
|
||||
|
||||
---
|
||||
|
||||
---
|
||||
|
||||
### 4. OrderDetail
|
||||
@@ -198,7 +204,25 @@ Before writing any SQL, create a simple Entity Relationship Diagram (ERD) to vis
|
||||
* Relationships between tables
|
||||
|
||||
This diagram does not need to be submitted, but it is strongly recommended as part of the database design process.
|
||||
|
||||
|
||||
## 📁 Project Structure
|
||||
|
||||
A suggested structure for the project:
|
||||
|
||||
- model
|
||||
- Database entity classes
|
||||
|
||||
- database
|
||||
- PostgreSQL connection management classes
|
||||
|
||||
- dao
|
||||
- JDBC database access classes
|
||||
|
||||
- service
|
||||
- Application business logic
|
||||
|
||||
- ui
|
||||
- Console user interface
|
||||
|
||||
## 💻 Required Features & App Flow
|
||||
|
||||
|
||||
Reference in New Issue
Block a user