Customer Service: Customer Domain #11/ Persistent layer, create entities

[A-Sakhmina]

The child task of Customer Service: Customer Domain#11.

Implement persistent layer, using Lombok, Spring Data annotations

Structures:

• Customer

  • id (PK)
  • name (varchar, max. length 30 chars, not-null)
  • surname (varchar, max. length 30 chars, not-null)
  • country_code_id (FK, not-null)
  • contact_details_id (FK, not-null)
  • createdAt (timestamp with timezone, UTC+0 only, not-null)
  • updatedAt (timestamp with timezone, UTC+0 only, not-null)

  Relations Country: Many-2-One ContactDetails: One-2-One

• Country

  • id (PK)
  • country_code (varchar, min.max. length 3 chars, not-null) // ISO 3166-1 alpha-3
  • name (varchar, max. length 30 chars, not-null)
  • createdAt (timestamp with timezone, UTC+0 only, not-null)
  • updatedAt (timestamp with timezone, UTC+0 only, not-null)

  Any purchase may be made in any possible country with different language support. Hence, internationalization (i18n) is crucial part of every single product. Because of that name attributes represent a key based on what a corresponding translation will be applied.

• ContactDetails

  • id (PK)
  • email (varchar, max. length 50 chars, email-pattern, not-null)
  • telegram_id // e.g. @testuser
  • createdAt (timestamp with timezone, UTC+0 only, not-null)
  • updatedAt (timestamp with timezone, UTC+0 only, not-null)

[A-Sakhmina]

1.application.properties

2. entities
3. Liquibase 3.1. changelog file master.xml(or yml) 3.2. add changelog files for create

Links

Use Liquibase to Safely Evolve Your Database Schema Liquibase + Spring Boot ➡ Настройка и написание миграций