U ؠhb @sddlmZmZddlZddlmZeedZeseddZeddZ ed d Z ed d Z ed dZ de de dede de ZeeZ ede ZedeedZeZeredeD] \ZZZedededqededeD],\ZZZeekredededqededed ed!ed"ed#ed$ed%ed&ned'W5QRXed(ed)dS)*) create_enginetextN) load_dotenv DATABASE_URLDB_HOSTZ localhostDB_PORTZ5432DB_NAMEZ timesheet_dbDB_USERZpostgres DB_PASSWORDz postgresql://:@/z'=== Quick Fix for Case Sensitivity === z21. Finding all case variations of developer IDs...a SELECT DISTINCT CAST(developer_id AS VARCHAR) as original_id, LOWER(CAST(developer_id AS VARCHAR)) as lower_id, COUNT(*) as records FROM activity_records WHERE LOWER(CAST(developer_id AS VARCHAR)) IN ('riddhidhakhara', 'ankita gholap', 'ankita_gholap') GROUP BY developer_id ORDER BY lower_id, original_id z Found these variations:z - 'z' (z records)z; 2. Option 1: Standardize all developer IDs to lowercase...z This would update:z' -> ''z Run this SQL to fix:z UPDATE activity_recordsz) SET developer_id = LOWER(developer_id)z- WHERE developer_id != LOWER(developer_id);z@ 3. Option 2: Update your API to handle case-insensitive queriesz Change your API queries from:z WHERE developer_id = :dev_idz To:z> WHERE LOWER(CAST(developer_id AS VARCHAR)) = LOWER(:dev_id)z) No records found for these developers!z! 4. RECOMMENDED FIX FOR YOUR API:a In your activity data API endpoint, update the query to be case-insensitive: Example for Python/SQLAlchemy: query = ''' SELECT * FROM activity_records WHERE LOWER(CAST(developer_id AS VARCHAR)) = LOWER(:dev_id) AND DATE(timestamp) BETWEEN :start_date AND :end_date ''' Example for raw SQL: WHERE LOWER(developer_id::varchar) = LOWER($1) This will match 'riddhidhakhara' with 'RiddhiDhakhara' or any other case variation. )Z sqlalchemyrrosZdotenvrgetenvrrrrr r ZengineprintZconnectZconnZexecuteresultZfetchallZ variationsZoriglowercountrr./quick_fix_case_sensitivity.pysL       "