-
Notifications
You must be signed in to change notification settings - Fork 3
Expand file tree
/
Copy pathTestChartPersistence.sql
More file actions
45 lines (42 loc) · 1.27 KB
/
TestChartPersistence.sql
File metadata and controls
45 lines (42 loc) · 1.27 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
-- Run this SQL query against your BlueMeter database to check if chart data is being saved
-- 1. Check recent encounters
SELECT
Id,
EncounterId,
BossName,
StartTime,
EndTime,
PlayerCount,
TotalDamage
FROM Encounters
ORDER BY StartTime DESC
LIMIT 5;
-- 2. Check if chart data exists for recent players
SELECT
Id,
EncounterId,
NameSnapshot,
TotalAttackDamage,
DPS,
-- Check if chart history JSON fields have data
CASE
WHEN DpsHistoryJson IS NULL THEN 'NULL'
WHEN DpsHistoryJson = '' THEN 'EMPTY'
WHEN LENGTH(DpsHistoryJson) > 0 THEN 'HAS DATA (' || LENGTH(DpsHistoryJson) || ' chars)'
END as DpsHistoryStatus,
CASE
WHEN HpsHistoryJson IS NULL THEN 'NULL'
WHEN HpsHistoryJson = '' THEN 'EMPTY'
WHEN LENGTH(HpsHistoryJson) > 0 THEN 'HAS DATA (' || LENGTH(HpsHistoryJson) || ' chars)'
END as HpsHistoryStatus
FROM PlayerEncounterStats
WHERE EncounterId IN (SELECT Id FROM Encounters ORDER BY StartTime DESC LIMIT 3)
ORDER BY TotalAttackDamage DESC;
-- 3. Sample one chart data JSON (first 500 chars)
SELECT
NameSnapshot,
SUBSTR(DpsHistoryJson, 1, 500) as DpsHistorySample
FROM PlayerEncounterStats
WHERE DpsHistoryJson IS NOT NULL
AND LENGTH(DpsHistoryJson) > 0
LIMIT 1;