I am specifying a table to retrieve a specific record but I am using a record ID from a different table (deliberately) and the response is retrieval of that record from the other table when I expect it to return a not found message. Is this by design? It is a problem for my use case. Any way to avoid this?
recACjz97bYmXXXX is an existing record in sessions table. The following curl targeting the profiles table returns the record from the sessions table instead of an error.
same result using below curl: