Admin/ocean-cleanup
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update tasks to reflect MySQL instead of PostgreSQL/PostGIS

Browse Source 
- Change task 22 from PostgreSQL+PostGIS to MySQL with spatial support
- Update references to PostGIS spatial queries to MySQL spatial functions
- Remove materialized view reference (MySQL specific)
- Update test task to reference MySQL instead of PostGIS
This commit is contained in:
Paul Bailey
2025-11-16 18:21:09 +00:00
parent 48e75465ab
commit 82a365f357
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
.kiro/specs/beach-litter-mapping/tasks.md
View File

@@ -173,7 +173,7 @@
## Backend API Development ## Backend API Development
- [ ] 21. Set up backend project structure - [x] 21. Set up backend project structure
- Initialize Node.js project with Express - Initialize Node.js project with Express
- Configure TypeScript for backend - Configure TypeScript for backend
- Set up folder structure: routes, controllers, services, middleware, utils - Set up folder structure: routes, controllers, services, middleware, utils
@@ -181,12 +181,12 @@
- Create environment configuration - Create environment configuration
- _Requirements: All backend requirements_ - _Requirements: All backend requirements_
- [ ] 22. Configure database with Prisma and PostGIS - [ ] 22. Configure database with Prisma and MySQL spatial support
- Set up PostgreSQL with PostGIS extension - Set up MySQL 8.0+ with spatial data support
- Create Prisma schema with all models (User, Report, Event, etc.) - Create Prisma schema with all models (User, Report, Event, etc.)
- Configure PostGIS geography types for location fields - Configure MySQL POINT spatial types for location fields
- Create database migrations - Create database migrations
- Set up database indexes for performance - Set up database indexes including spatial indexes for performance
- _Requirements: 1.1, 2.1, 3.2, 4.1_ - _Requirements: 1.1, 2.1, 3.2, 4.1_
- [ ] 23. Implement authentication system - [ ] 23. Implement authentication system
@@ -203,7 +203,7 @@
- Build GET /api/reports/:id for single report retrieval - Build GET /api/reports/:id for single report retrieval
- Create PATCH /api/reports/:id for updates - Create PATCH /api/reports/:id for updates
- Implement DELETE /api/reports/:id with authorization - Implement DELETE /api/reports/:id with authorization
- Add spatial queries using PostGIS for location-based filtering - Add spatial queries using MySQL spatial functions for location-based filtering
- _Requirements: 1.1-1.8, 2.1, 2.4_ - _Requirements: 1.1-1.8, 2.1, 2.4_
- [ ] 25. Implement file upload and EXIF processing - [ ] 25. Implement file upload and EXIF processing
@@ -232,9 +232,9 @@
- [ ] 28. Build hotspot calculation system - [ ] 28. Build hotspot calculation system
- Create scheduled job with node-cron for hotspot calculations - Create scheduled job with node-cron for hotspot calculations
- Implement PostGIS spatial queries to identify clusters - Implement MySQL spatial queries to identify clusters
- Calculate severity scores based on report count and frequency - Calculate severity scores based on report count and frequency
- Store hotspot data in database or materialized view - Store hotspot data in database
- Create GET /api/analytics/hotspots endpoint - Create GET /api/analytics/hotspots endpoint
- _Requirements: 3.2, 3.3, 3.4_ - _Requirements: 3.2, 3.3, 3.4_
@@ -310,7 +310,7 @@
- Create API endpoint tests with Supertest - Create API endpoint tests with Supertest
- Test authentication flows - Test authentication flows
- Test file upload pipeline - Test file upload pipeline
- Test spatial queries with PostGIS - Test spatial queries with MySQL
- Test external API integration with mocks - Test external API integration with mocks
- _Requirements: All requirements_ - _Requirements: All requirements_