Hi, It is very convenient for me to use GeometryField as I can save any geometry type into the same field. The database logic will become more complex if I am required to create a separate table or field for e.g. points and linestrings.
Still looking for a workaround, or is there a reason for me not to save all geometries into the same field? On Thursday, August 23, 2012 2:27:48 AM UTC+3, Melvyn Sopacua wrote: > > On 22-8-2012 10:31, geonition wrote: > > > I have a problem with GeometryField not showing the saved geometry in > the > > admin interface. The problem is that the GeometryField has a type of > > 'GEOMETRY' when the value saved might have the type of e.g. 'POINT'. > > The GeometryField is like the normal Field class: the base class for > actual fields you should be using in your model, like PointField. The > docs are not very clear on this issue. > -- > Melvyn Sopacua > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/WJauvt8Cs1QJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
