nidus-sync/db/sql/traplocation_by_source_id.sql

-- TrapLocationBySourceID
SELECT 
	tl.globalid AS trap_location_globalid,
	ST_Distance(pl.geospatial, tl.geospatial) AS distance
FROM 
	fieldseeker.pointlocation pl
CROSS JOIN
	fieldseeker.traplocation tl
WHERE 
	tl.organization_id = $1 AND
	pl.globalid = $2
ORDER BY 
	ST_Distance(pl.geospatial, tl.geospatial)
LIMIT 4
Add trap count data to source page It's...way too many rows, now that I have the actual data. It needs to be reworked. 2025-11-20 20:59:28 +00:00			`-- TrapLocationBySourceID`
			`SELECT`
			`tl.globalid AS trap_location_globalid,`
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those. 2025-12-24 17:49:39 -07:00			`ST_Distance(pl.geospatial, tl.geospatial) AS distance`
Add trap count data to source page It's...way too many rows, now that I have the actual data. It needs to be reworked. 2025-11-20 20:59:28 +00:00			`FROM`
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those. 2025-12-24 17:49:39 -07:00			`fieldseeker.pointlocation pl`
Add trap count data to source page It's...way too many rows, now that I have the actual data. It needs to be reworked. 2025-11-20 20:59:28 +00:00			`CROSS JOIN`
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those. 2025-12-24 17:49:39 -07:00			`fieldseeker.traplocation tl`
Add trap count data to source page It's...way too many rows, now that I have the actual data. It needs to be reworked. 2025-11-20 20:59:28 +00:00			`WHERE`
			`tl.organization_id = $1 AND`
			`pl.globalid = $2`
			`ORDER BY`
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those. 2025-12-24 17:49:39 -07:00			`ST_Distance(pl.geospatial, tl.geospatial)`
Add trap count data to source page It's...way too many rows, now that I have the actual data. It needs to be reworked. 2025-11-20 20:59:28 +00:00			`LIMIT 4`