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
The idea here is that hitting /content without a ?sql= will show an empty result set AND default to including a bunch of extras about the list of tables in the database.
Then I won't have to think about /content and /content?sql= as separate pages any more.
The text was updated successfully, but these errors were encountered:
Changed my mind on this - I'm going to have the query_view mapped to /db but have the first code on there notice if ?sql= is missing and return a database_view() function instead.
* Refs #2111, closes#2110
* New Context dataclass/subclass mechanism, refs #2127
* Define QueryContext and extract get_tables() method, refs #2127
* Fix OPTIONS bug by porting DaatbaseView to be a View subclass
* Expose async_view_for_class.view_class for test_routes test
* Error/truncated aruments for renderers, closes#2130
Refs:
The idea here is that hitting
/content
without a?sql=
will show an empty result set AND default to including a bunch of extras about the list of tables in the database.Then I won't have to think about
/content
and/content?sql=
as separate pages any more.The text was updated successfully, but these errors were encountered: