# MySQL prog2 — Data Freshness Analysis
# Date: 2026-09-07

## Method

MySQL `information_schema.tables` has `create_time` and `update_time` but:
- Most tables have `update_time` = NULL (MySQL doesn't track by default)
- `create_time` shows when table was created, not last data change
- Need to check actual data timestamps for freshness

## Table Creation Dates

### Newest Tables (2022-2023)

| Database | Table | Created |
|----------|-------|---------|
| apps_master | bridging_division_brandid | 2023-04-18 |
| apps_master | m_server_kredivo | 2023-03-06 |
| apps_master | m_outlet1 | 2023-01-10 |
| apps_master | m_pharos_division | 2023-01-10 |
| apps_transaction | reprocess_order_sp | 2022-12-12 |
| apps_transaction | log_download_detail | 2022-12-02 |
| apps_master | M_MaximumPlafon_PerOutlet | 2022-12-01 |
| apps_transaction | download_order_neogenesis | 2022-11-23 |

### Oldest Tables (2018)

| Database | Table | Created |
|----------|-------|---------|
| sayasehat | akucantik_sessions | 2018-03-14 |
| sayasehat | admin_tb | 2018-03-14 |
| sayasehat | article_detail_log | 2018-03-14 |

## Analysis

| Period | Tables | Notes |
|--------|--------|-------|
| 2023 | 4 | Recent additions |
| 2022 | 26 | Active development |
| 2018-2021 | ~2,000 | Legacy |

## Data Freshness (Actual)

Need to check data timestamps in specific tables:

| Table | Check | Result |
|-------|-------|--------|
| ecommerce.tokopedia_product | MAX(updated_at) | TBD |
| pharmanet.m_user | MAX(last_login) | TBD |
| century.m_member | MAX(created_at) | TBD |
| absensi.hadir | MAX(date) | TBD |

## Conclusion

**Most tables are legacy** (2018-2021). Recent additions are from 2022-2023. Actual data freshness requires checking timestamp columns in each table.

## Next Steps

1. **Check data timestamps** — MAX(updated_at) in key tables
2. **Identify live tables** — tables with recent data
3. **Focus on live data** — for negotiation leverage