Open yorek opened 1 year ago
Tracking support for geography data type: https://github.com/Azure/data-api-builder/issues/1397
@yorek,
The exclude
list says the field is NOT authorized for access by anonymous role. It does NOT mean we exclude it from being available in the schema.
In a different config, its possible that you might want to exclude it from anonymous role but include it for some other role. Hence, we always gather the metadata in the schema. We don't analyze the entire config to determine if its not needed at all by any role - that would be a perf hit at startup.
Adding support for the data type should be prioritized over this issue since that will solve this problem.
todo: in schema generation, don't validate/resolve unsupported type if field is excluded.
May be more involved depending on the order of db metadata resolving versus permissions processing. db metadata process may take place before permissions.
in the interim, since supported geo/spatial types is more involved (extra .DLL which only works on Windows?) , the action here would be to improve the returned error message. Instead of multiple errors/stack traces , a single error should be printed:
Entity: "Positions" | Database Object Source: "dbo.vehicle_position_data" | Column: "position" | Unsupported column type.
While unsupported column type is geography::Point
, that value doesn't seem to be returned by the schema fetcher mechanism. We may not be able to output the type in the error message. When this issue is picked up, please check in the debugger for any usable values.
What happened?
My table is the following:
The
geography
data type is not yet supported, so I added theposition
column to the excluded columns:But I get the error:
Which is not expected as the column has been excluded.
Version
0.7.5
What database are you using?
Azure SQL
What hosting model are you using?
Local (including CLI)
Which API approach are you accessing DAB through?
REST
Relevant log output
Code of Conduct