Skip to main content
reformatted so the sql statement can be read without scrolling to the right
Source Link
underdark
  • 84.5k
  • 22
  • 233
  • 415

As previously mentioned, mixed Geometries in one layer are not supported by QGIS.

If you have strong use case for keeping all of the data in a single table, another option to creating new tables (as suggested by @Benno) would be to create views referencing each geometry type from the initial table:

CREATE VIEW vwPoints  
SELECT <fields>  
FROM initial_table  
WHERE ST_GeometryType(geom) = 'ST_Point'

I am not sure about is the performance implications of going with views vs. individual tables, but that is something you could easily experiment with and decide which route you want to take.

As previously mentioned, mixed Geometries in one layer are not supported by QGIS.

If you have strong use case for keeping all of the data in a single table, another option to creating new tables (as suggested by @Benno) would be to create views referencing each geometry type from the initial table:

CREATE VIEW vwPoints SELECT <fields> FROM initial_table WHERE ST_GeometryType(geom) = 'ST_Point'

I am not sure about is the performance implications of going with views vs. individual tables, but that is something you could easily experiment with and decide which route you want to take.

As previously mentioned, mixed Geometries in one layer are not supported by QGIS.

If you have strong use case for keeping all of the data in a single table, another option to creating new tables (as suggested by @Benno) would be to create views referencing each geometry type from the initial table:

CREATE VIEW vwPoints  
SELECT <fields>  
FROM initial_table  
WHERE ST_GeometryType(geom) = 'ST_Point'

I am not sure about is the performance implications of going with views vs. individual tables, but that is something you could easily experiment with and decide which route you want to take.

added 1 characters in body
Source Link
RyanKDalton
  • 23.2k
  • 17
  • 112
  • 180

As previously mentioned, mixed Geometries in one layer are not supported by QGIS.

If you have strong use case for keeping all of the data in a single table, another option to creating new tables (as suggested by @Benno) would be to create views referencing each geometry type from the initial table:

CREATE VIEW vwPoints SELECT <fields> FROM initial_table WHERE ST_GeometryType(geom) = 'ST_Point'ST_Point'

I am not sure about is the performance implications of going with views vs. individual tables, but that is something you could easily experiment with and decide which route you want to take.

As previously mentioned, mixed Geometries in one layer are not supported by QGIS.

If you have strong use case for keeping all of the data in a single table, another option to creating new tables (as suggested by @Benno) would be to create views referencing each geometry type from the initial table:

CREATE VIEW vwPoints SELECT <fields> FROM initial_table WHERE ST_GeometryType(geom) = 'ST_Point

I am not sure about is the performance implications of going with views vs. individual tables, but that is something you could easily experiment with and decide which route you want to take.

As previously mentioned, mixed Geometries in one layer are not supported by QGIS.

If you have strong use case for keeping all of the data in a single table, another option to creating new tables (as suggested by @Benno) would be to create views referencing each geometry type from the initial table:

CREATE VIEW vwPoints SELECT <fields> FROM initial_table WHERE ST_GeometryType(geom) = 'ST_Point'

I am not sure about is the performance implications of going with views vs. individual tables, but that is something you could easily experiment with and decide which route you want to take.

Source Link
RyanKDalton
  • 23.2k
  • 17
  • 112
  • 180

As previously mentioned, mixed Geometries in one layer are not supported by QGIS.

If you have strong use case for keeping all of the data in a single table, another option to creating new tables (as suggested by @Benno) would be to create views referencing each geometry type from the initial table:

CREATE VIEW vwPoints SELECT <fields> FROM initial_table WHERE ST_GeometryType(geom) = 'ST_Point

I am not sure about is the performance implications of going with views vs. individual tables, but that is something you could easily experiment with and decide which route you want to take.