On a related note, I noticed that including a foreign key field in "read_only_fields" nukes the "queryset" kwarg:

I understand why having this attribute is notrequired for a read-only field, but what is the harm in keeping it? Nuking this attribute removes the link to the foreign model and makes it much harder to generate a schema for the output of a serializer.

@jlaine Just on your related note: my immediate thought is that ifread_only_fields is misbehaving for you is to explicitly declare the field.read_only_fields is a short-cut, it's task is to cover the common-case. The canonical approach is always to explicitly declare the field.

If that doesn't suit then put together a proper description and open a new ticket and we'll have a look.

Thanks for merging this! Concerning the read_only_fields, explicitly declaring the field doesn't help : there is code to prevent you from providing a queryset on a field you declare as read_only. Not sure what the rationale is:

OK. Open a new ticket and we’ll think it through