Instruction vs. Solution Inconsistency in the Student Streaks Analysis SQL Project

1) The first issue concerns the streak logic. On the real platform, a streak increments only on consecutive days that a user engages. In this project, however, streaks are calculated based on the streak_created column, which includes multiple records on the same day with different hours and may also contain gaps between days. These gaps and same-day duplicates do not break the streak counting, making the project’s streak logic different from the platform’s actual behavior.

Aside from the streak logic:
2) In this project: Student Streaks Analysis with SQL Project in the instruction a paragraph mentions: 
- Calculating Longest Streaks: Calculate each user’s most extended streak length. The metric’s duration increments each day the user remains active, and they haven’t frozen their streak manually to preserve their progress. The length is not extended when there’s no new interactions or when the streak is frozen. 

However, in the provided solution, the streak_frozen column is not taken into account at all. This approach would only be acceptable if streak_active were automatically NULL whenever streak_frozen = 1. 

But in the dataset, there are four records where both streak_active = 1 and streak_frozen = 1, meaning the user engaged with the platform despite having frozen their streak. According to the instructions, these days should not have incremented the streak, yet the solution counts them.