dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #11551 from supabase/fix/postgis-guide

Browse Source 
fix: correct SQL syntax for creating seed data in PostGIS guide
This commit is contained in:
Tyler authored and GitHub committed 2023-01-10 13:01:14 +09:00
2 parents 80d499bbb1 884b5d8ede
commit 98009e7514
1 file changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/pages/guides/database/extensions/postgis.mdx
+4 -4
View File
@@ -95,9 +95,9 @@ You can insert geographical data through SQL or through our API.
insert into public.restaurants
(name, location)
values
('Supa Burger', st_point(-73.946823 40.807416)),
('Supa Pizza', st_point(-73.94581 40.807475)),
('Supa Taco', st_point(-73.945826 40.80629));
('Supa Burger', st_point(-73.946823, 40.807416)),
('Supa Pizza', st_point(-73.94581, 40.807475)),
('Supa Taco', st_point(-73.945826, 40.80629));
```
</TabPanel>
@@ -143,7 +143,7 @@ await supabase.from('restaurants').insert([
</TabPanel>
</Tabs>
Notice the order in which you pass the latitude and longitude. Longitude comes first, and is because longitude represents the x-axis of the location. Another thing to watch for is that there is no comma between the two values, just a single space.
Notice the order in which you pass the latitude and longitude. Longitude comes first, and is because longitude represents the x-axis of the location. Another thing to watch for is when inserting data from the client library, there is no comma between the two values, just a single space.
At this point, if you go into your Supabase dashboard and look at the data, you will notice that the value of the `location` column looks something like this.