Create Database Tables for Storing Period and Ovulation Predictions

[EmmaTellblom]

Title

Create Database Tables for Storing Period and Ovulation Predictions

Description

To enhance user experience by showing the difference between expected and actual dates for periods and ovulation, we need to create two new database tables. These tables will store both period and ovulation predictions.

Objectives

• Create Tables: Develop and integrate two new database tables to store period and ovulation predictions.
• Track Predictions: Ensure that both predicted and actual dates are stored for comparison.

Required Tables

Period Predictions Table

• Table Name: period_predictions
• Purpose: Store predicted dates for periods.
• Fields:
  • id: Unique identifier for each prediction (Primary Key).
  • date: The predicted date for the next period.
  • cycle_id: Reference to the cycle for which the prediction is made. (forgeign key)

Ovulation Predictions Table

• Table Name: ovulation_predictions
• Purpose: Store predicted dates for ovulation.
• Fields:
  • id: Unique identifier for each prediction (Primary Key).
  • date: The predicted date for ovulation.
  • cycle_id: Reference to the cycle for which the prediction is made. (forgeign key)

Requirements

• Database Schema: Define and implement the schema for both tables in the database.
• Data Integration: Ensure that predictions are stored in these tables and updated based on new data.

Acceptance Criteria

• New database tables period_predictions and ovulation_predictions are created and integrated into the existing database.
• The system accurately stores and retrieves prediction and actual dates.

Additional Notes

• Ensure that the database schema aligns with existing design patterns and practices.
• Consider any necessary migrations or updates to existing data structures.
• Test the implementation thoroughly to ensure accuracy and reliability of stored predictions.

Please provide feedback or additional suggestions on the table design and implementation.

[ljubitje]

Is this necessary? Amount of data required for calculation is minimal. Is calculation + comparison not fast enough to be done on the fly? Perhaps designing the equations smartly could even hold current calculated values to minimize new calculations to triviality.