Open firrae opened 4 years ago
I managed to find a solution that included me creating a custom search lambda, though I'm curious if that is the best way to handle this going forward? I don't see us having to do this much, if at all, ever again, but I'd like to know just in case.
NameError (wrong constant name c)
From your code here it should be Client.first_name
and Client.last_name
(for the record.client_id
relation)
The source
key represents the table and the column implied in the relation in order to build a SQL query.
Maybe it's clearer like that :)
Hi there,
Currently, due to the way the current application stacks are structured, I need to do a custom join in my data fetch query but I find that when I do this I cannot get search to work at all. The generated file says the following:
I have my custom join aliased but when I use the alias it returns:
The following is my data tables class:
I can get it to at least load by removing the
c
fromfirst_name
andlast_name
inview_columns
, but searching never works even with this change. Instead it just returns:Any help in figuring out what I'm doing wrong would be greatly appreciated.