[FEAT] Database Setup - Models, and Seeding

[lurldgbodex]

Description

Set up a database management system for our Spring Boot project using Hibernate ORM. The task includes configuring the database connection, creating entity classes, and seeding the database with initial data. This setup will help streamline data operations and ensure application can interact with the database efficiently.

Tasks

Database Configuration

• Configure the application to connect to a PostgreSQL database by default.

• Allow the setup to be flexible for configuring any database.

• Add necessary dependencies in pom.xml (Spring Data JPA, PostgreSQL Driver).

• Update application.properties with database connection details (URL, username, password, etc.).

• Set spring.jpa.hibernate.ddl-auto=update for automatic schema management.

  Entity Classes

• Create entity classes for User, Profile, Organisation, and Product.

• Annotate the classes with Hibernate/JPA annotations (@Entity, @Table, @Id, etc.).

• Define relationships between entities:

  • A user has one profile (@OneToOne).
  • A user has many products (@OneToMany).
  • A user belongs to many organisations (@ManyToMany).
  • An organisation has many users (@ManyToMany).

  Repository Layer

• Create repository interfaces extending JpaRepository for each entity.

• Define custom queries if necessary.

  Seeding the Database

• Create a data seeding component to initialize the database with sample data.

• Ensure the seeding process runs only once during application startup.

• Seed the database with the following data:

  • At least 2 users.
  • At least 2 products per user.
  • At least 3 organisations.
  • User one belongs to 2 of the organisations.
  • User two belongs to all 3 organisations.

Validation Steps

- Ensure the following tables and constraints are created:
    * Users
    * Profiles
    * Organisations
    * Products
- Validate the relationships:
    * A user has one profile.
    * A user has many products.
    * A user belongs to many organisations.
    * An organisation has many users.

Api Endoint

• implement the endpoint
  • [GET] api/v1/users/user_one_id
  • Sample Response

{
  "name": "John Doe",
  "id": "some-user-id",
  "email": "johndoe@example.com",
  "profile": {
    "first_name": "John",
    "last_name": "Doe",
    "phone": "1234567890",
    "avatar_url": "http://example.com/avatar.jpg"
  },
  "organisations": [
    {
      "org_id": "some-org-id-1",
      "name": "Some Org",
      "description": "Some Org Description"
    },
    {
      "org_id": "some-other-org-id-2",
      "name": "Some Other Org",
      "description": "Some Other Org Description"
    }
  ],
  "products": [
    {
      "product_id": "some-product-id",
      "name": "Some Product",
      "description": "Some Product Description"
    },
    {
      "product_id": "some-other-product-id",
      "name": "Some Other Product",
      "description": "Some Other Product Description"
    }
  ]
}

• [GET] api/v1/users/user_two_id
  • Sample Response

    {
    "name": "John Doe",
    "id": "some-user-id",
    "email": "johndoe@example.com",
    "profile": {
    "first_name": "John",
    "last_name": "Doe",
    "phone": "1234567890",
    "avatar_url": "http://example.com/avatar.jpg"
    },
    "organisations": [
    {
    "org_id": "some-org-id-1",
    "name": "Some Org",
    "description": "Some Org Description"
    },
    {
    "org_id": "some-other-org-id-2",
    "name": "Some Other Org",
    "description": "Some Other Org Description"
    },
    {
    "org_id": "some-other-org-id-3",
    "name": "Some Other Org",
    "description": "Some Other Org Description"
    }
    ],
    "products": [
    {
    "product_id": "some-product-id",
    "name": "Some Product",
    "description": "Some Product Description"
    },
    {
    "product_id": "some-other-product-id",
    "name": "Some Other Product",
    "description": "Some Other Product Description"
    }
    ]
    }

Testing

• Verify the database connection and entity mappings by running the application.
• Ensure data is correctly seeded into the database.
• Validate the relationships and data integrity.

Acceptance Criteria:

• The application should successfully connect to the PostgreSQL database.
• Entity classes should accurately represent the database schema.
• The database should be seeded with initial data upon application startup.
• All configurations and code should follow best practices and be well-documented.
• The database schema should include the required tables and relationships.
• The seeded data should meet the specified criteria.

Assignees

@lurldgbodex

[nedssoft]

@lurldgbodex you omitted the endpoint specs for the validation?

[lurldgbodex]

@nedssoft i have added the endpoint specs and i have pushed the code and made pull request