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
then executed bin/console doctrine:generate:entities... and bin/console doctrine:schema:update.
Now in the Postgres DB I have a new geomshape field of geography type but it's comment is DC2Type:geometry.
Problem is that on the next time I use bin/console doctrine:schema:update it wants to alter geomshape field to type Geography again:
ALTERTABLE geo_objects ALTER geomshape TYPE Geography;
And again, every time I use d:s:u. Is this my fault (perhaps misconfiguration) or a bug?
The text was updated successfully, but these errors were encountered:
forsetius
changed the title
Doctrine repeatly creates geometry-type field
Doctrine repeatly alters geography-type field
Sep 27, 2017
Nope, I tried to use @jsor 's solution with commented: false but to no avail. Then I deleted the field and allowed Doctrine to create it again. Now, the comment was correctly (DC2Type:geography). Then I commented out that commented: false and deleted and created field. Again, the comment was correct. Anyway, once correctly created, the Doctrine doesn't want to alter it again. Solved
Then I remembered that last week I changed the type of this field from geometry to geography. Turns out that Doctrine didn't update the comment. I don't know if it is something on this bundle or Doctrine's side. If you think it is on Doctrine side, please close this issue.
Having configured the bundle:
in entity class I defined a field:
then executed
bin/console doctrine:generate:entities...
andbin/console doctrine:schema:update
.Now in the Postgres DB I have a new
geomshape
field ofgeography
type but it's comment isDC2Type:geometry
.Problem is that on the next time I use
bin/console doctrine:schema:update
it wants to altergeomshape
field to typeGeography
again:And again, every time I use
d:s:u
. Is this my fault (perhaps misconfiguration) or a bug?The text was updated successfully, but these errors were encountered: