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
I think it would be possible to support basic foreign key joins on the table page.
The user could specify columns that should result in a join (from a set of suggestions similar to how facets work right now) and they could then be passed as ?_join=city_id arguments.
This feature will make a lot of sense when combined with the ability to show / hide / customize columns, see #292
The text was updated successfully, but these errors were encountered:
With ?_join=city_id the underlying query would become this:
select
facetable.pk as 'facetable.pk',
facetable.created as 'facetable.created',
facetable.planet_int as 'facetable.planet_int',
facetable.on_earth as 'facetable.on_earth',
facetable.state as 'facetable.state',
facetable.city_id as 'facetable.city_id',
facetable.neighborhood as 'facetable.neighborhood',
facetable.tags as 'facetable.tags',
facetable.complex_array as 'facetable.complex_array',
facet_cities.id as 'facet_cities.id',
facet_cities.name as 'facet_cities.name'
from
facetable
join facet_cities on facetable.city_id = facet_cities.id
I'm using select foo.bar as 'foo.bar' here to ensure that every column has an unambiguous name, to avoid any weirdness from joining against a table where both tables have a 'name' column.
I think it would be possible to support basic foreign key joins on the table page.
The user could specify columns that should result in a join (from a set of suggestions similar to how facets work right now) and they could then be passed as
?_join=city_id
arguments.This feature will make a lot of sense when combined with the ability to show / hide / customize columns, see #292
The text was updated successfully, but these errors were encountered: