-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SRID POINT Mysql 8+ Not saved #17
Comments
Hello, Currently the MySQL code doesn't use the SRID value. This is something that'll need to be implemented. Currently SRID are saved, but they aren't persisted. We have to enhance the convertToDatabaseValueSQL in the MySQL classes for the Geographic types, but if someone wants to contribute, he should be careful and check the MySQL functionalities, because I remember that it wasn't compliant with first versions of MySQL5. I even don't know if SRID are now compliant with MySQL5.* |
saving srid for MySQL is critical, because it affects on lat/lon order. see:
PS: also it is possible to define SRID in MySQL column definition, like:
see: https://dev.mysql.com/doc/refman/8.4/en/spatial-type-overview.html
|
Yes, it is. I'm currently working on it. MySQL has its own method to store data and Doctrine ORM only accepts one parameter, I cannot store coordinates and SRID with the current engine. So, I'm working on sub-libraries to convert the point into the internal binary storage system of MySQL. IMO, I still need 7 or 8 days of development to make it working. But I only work on it on my free time. |
If you're waiting for this new feature, you can yet use the SRID method with a second argument. This is not a good solution, but this is a temporary way to do it. (The best way, currently, is to update your column to specify a default SRID) |
Mysql 8 can save PONT like this: ST_SRID(POINT(...), 4326)
But
Not working - SRID did not saved
The text was updated successfully, but these errors were encountered: