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
This would be a bit easier if I moved all code in Datasette that loops through a list of tables to consult the internal database catalog tables for those, then I could include these unreadable tables in that but have a "unreadable = 1" column which could be used to filter them out.
The purpose of those catalog tables is to support things like efficently searching and paginating through all available tables. Having internal methods that use them to list tables would also help with this challenge of knowing when to skip tables that depend on not-installed extensions.
This came up just now here:
Originally posted by @simonw in #2388 (comment)
The purpose of those catalog tables is to support things like efficently searching and paginating through all available tables. Having internal methods that use them to list tables would also help with this challenge of knowing when to skip tables that depend on not-installed extensions.
datasette/docs/internals.rst
Lines 1370 to 1383 in 05dfd34
The text was updated successfully, but these errors were encountered: