You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to add a SRID attribute with the value of 0 to a column in my database.
I tried doing so by writing the following in a migration:
$table->point('coordinate', 0);
I discovered that this didn't work and I had to dive into why this was the case.
I found the culprit in the MySqlGrammer. It rather silently ignores my attempt to set the SRID to 0.
For now, I'm just using DB::statement(...) to achieve my goal, but I'm wondering if there is any particular reason why the modifySrid method requires the SRID value to be greater than 0?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone.
I was trying to add a SRID attribute with the value of 0 to a column in my database.
I tried doing so by writing the following in a migration:
I discovered that this didn't work and I had to dive into why this was the case.
I found the culprit in the MySqlGrammer. It rather silently ignores my attempt to set the SRID to 0.
For now, I'm just using
DB::statement(...)
to achieve my goal, but I'm wondering if there is any particular reason why themodifySrid
method requires the SRID value to be greater than 0?Beta Was this translation helpful? Give feedback.
All reactions