Geometry is converted to Geography
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 4.5k
- Forks
- 884
- PR merge metrics
- No merged PRs in 30d
Description
Hi.
I would like to use geometry type in Postgresql.
However geometry seems to be replaced by geography.
I want to use ST_CONTAINS(geometry, geometry)
But it can not be used in Geography
I do not want to cast because I want to process a large amount of data
Is there a function that deserves st_contains that can be used with geography type or how to create a table with geometry?
thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/Phinx/Db/Adapter/PostgresAdapter.php around lines 951-962 and trace how PostgreSQL spatial types are mapped during table creation. Reproduce the reported geometry-to-geography conversion with ST_CONTAINS; done means a migration can create a geometry column without requiring a cast.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100