Thanks - I am not sure why this 'gist' is used when creating index tbf. I
dont see any special difference w/o it. Will investigate further though.
Hope this might help if someone bumps into same problem.
Kindest regards
On Thu, Jan 24, 2019 at 6:21 PM Mike Bayer wrote:
> On Thu, Jan 24, 2019 at
On Thu, Jan 24, 2019 at 12:15 PM Nikola Radovanovic wrote:
>
> Hi,
> you are right: I found that geoalchemy2 automatically creates indexes; which
> I eventually turned off in model, using e.g.
>
> polygon = Column(Geometry(geometry_type='POLYGON', srid=3857,
> spatial_index=False))
>
> and addin
Hi,
you are right: I found that geoalchemy2 automatically creates indexes;
which I eventually turned off in model, using e.g.
polygon = Column(Geometry(geometry_type='POLYGON', srid=3857,
spatial_index=False))
and adding them manually to migration script:
sa.Column('polygon', Geometry(geometry
On Thu, Jan 24, 2019 at 4:17 AM Nikola Radovanovic wrote:
>
> Hi all,
> I have a need to use PostGIS extension in order to get support for objects
> like Point and Polygon provided by geoalchemy2 in PostgreSql.
>
> Now, the issue I encounter is that while migrating model which uses
> Point/Polyg
Hi all,
I have a need to use PostGIS extension in order to get support for objects
like Point and Polygon provided by geoalchemy2 in PostgreSql.
Now, the issue I encounter is that while migrating model which uses
Point/Polygon (classes derived from UserDefinedType) - geoalchemy2 tries to
creat
