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
Ideally, the geometry_field can be automatically selected from geometry_columns table with the corrent table parameter, but the setting above only works in the previous mapnik versions.
PostGIS & PGraster: The table/geometry_table/raster_table parameter in XML style must be quoted if it would need quoting in SQL query
But when using postgis outside of mapnik, I do not need to add quotes for the non English characters in query statements.
The current version of sql_utils::table_from_sql(source) uses the regular expression re_table_name(source) to match the table and schema name:
\s*
(\w+|("[^"]*")+)
(\.(\w+|("[^"]*")+))?
\s*
where \w only matches [A-Z a-z 0-9_]. I have to either add quotes, manually set geometry_field parameter, or revert back to use the old version of the function sql_utils::table_from_sql.
Is this the expected behaviour?
The text was updated successfully, but these errors were encountered:
I have a postgis table named
注记5
. I'm using postgis datasource with parameter:Ideally, the
geometry_field
can be automatically selected fromgeometry_columns
table with the correnttable
parameter, but the setting above only works in the previous mapnik versions.I have noticed this API changes between v3.0 and v3.1, which says:
But when using postgis outside of mapnik, I do not need to add quotes for the non English characters in query statements.
The current version of
sql_utils::table_from_sql
(source) uses the regular expressionre_table_name
(source) to match the table and schema name:where
\w
only matches[A-Z a-z 0-9_]
. I have to either add quotes, manually setgeometry_field
parameter, or revert back to use the old version of the functionsql_utils::table_from_sql
.Is this the expected behaviour?
The text was updated successfully, but these errors were encountered: