Roberto Blasco wrote:The final goal is to add "filters" features in my tables in order to make the clients possible to find any data through fields and relations. With the possibility of grouping that filters and store those groups as custom searchs.
I don't know the level of knowledge your clients have on databases and/or table structures, but since tables always hold pk/fk and probably one or more other technical fields, I would never expose all columns to my users.
This functionality could have a better UX by creating tables for a data dictionary. In these tables you could store tablenames, column names (with user-friendly labels) and also relations between tables.
Another advantage is that you decide what columns will be available to search on, columns lacking indexes could have poor performance when searching for content.
Just an idea to make things little easier overall.
Although it involves more tables/UI, the possibility to limit the number of columns means you don't have to catch specific errors your clients would make otherwise.