- Do NOT create, alter, or drop any tables
- Do NOT modify existing table structures
- Do NOT run database migration scripts
- The database is already properly set up and working
- Only use the existing database connection through
backend/config/database.js
drug_id, drug_name, dosage, form, manufacturer, base_price, category_id, image_path
inventory_id, batch_id, drug_id, stock_level, expiry_date, reorder_level, date_received
order_id, account_id, order_date, discount, total_amount
order_detail_id, inventory_id, quantity, order_id, unit_price
pharmacist_id, first_name, last_name, phone_number, email, license_number
order_id, payment_type_id, amount_paid, change_amount
payment_type_id, payment_type
category_id, category_name
account_id, username, password, pharmacist_id, is_active, role, created_at, updated_at, last_login
- Use
backend/config/database.js
for all database connections
- Never create new database connection files
- Use the existing connection pool
- Follow existing project structure in
backend/
folder
- Use consistent naming conventions that match the database schema
- Maintain existing API route structure in
backend/routes/
- Build APIs that work with the existing table structure
- Use proper SQL queries that match the exact column names
- Handle database relationships according to the existing schema
- Keep backend code in
backend/
directory
- Use existing middleware from
backend/middleware/
- Store uploads in
backend/uploads/
- Maintain logs in
backend/logs/
- Never create database setup/migration scripts
- Never modify package.json to add database setup commands
- Never suggest database schema changes
- Never create alternative table structures
- Never ignore the existing column names
- Always refer to the exact table and column names listed above
- Use the existing database connection configuration
- Write SQL queries that match the existing schema
- Respect the current relationships between tables
- Follow the established project structure
This is a Pharmacy Management System with:
- Inventory management for medicines
- Order processing and payment handling
- User account management with roles
- Pharmacist information tracking
- Category-based medicine organization
The database is already working properly and should remain unchanged.