Django ORM - explain on your fingers how this query to the database (PostgreSQL) should look like?

Question

PostgreSQL

Dear Toasters (c. Battlestar Galactica), I'm slowly but surely moving to the "bright side", but django-photologue is on the way to enlightenment.
I am writing a django application (car rental service), using django-photologue to manage images. I don’t understand how to select one photo related to this gallery through a gallery attached via foreign_key. ( Need a Django ORM solution )
To clarify the situation, the following tables are available:
My car model:

class Car(models.Model):
    manufacturer = models.ForeignKey(CarManufacturer, verbose_name='Araç markası')
    .......

    gallery = models.ForeignKey(Gallery, verbose_name='Resimler')

    .......
    available = models.BooleanField(verbose_name='Araç mevcut')
    is_rented = models.BooleanField(verbose_name='Araç kiralanabilir mi')
    add_to_main = models.BooleanField(verbose_name='Anasayfaya ekle')
    under_maintance = models.BooleanField(verbose_name='Araç servis dışı mıdır')
    ...........
    ...........

django-photologue models to be bound to (from the official release)

class Gallery(models.Model):
...........
    photos = SortedManyToManyField('Photo', related_name='galleries', 
                      verbose_name=_('photos'), null=True, blank=True)
...........


class Photo(ImageModel):
    title = models.CharField(_('title'),   max_length=50, unique=True)
    slug = models.SlugField(_('slug'), unique=True)
    ...........
    def get_absolute_url(self):
        return reverse('pl-photo', args=[self.slug])
    ...........

As can be seen from the links, each car (Car model) has its own image gallery (Gallery model), which in turn has N-th number of images through a many-to-many relationship (Photo model).
Attention, question
Dear experts, how should the following query to the database look like using django-ORM

cursor = connection.cursor()
    cursor.execute ('''SELECT  DISTINCT ON (cars_car)
              cars_car.id AS id,
              cars_carmanufacturer.name AS manufacturer,
              cars_carmodel.name AS model,
              photologue_photo.image AS photo
            FROM
              cars_car,
              photologue_photo,
              photologue_gallery_photos,
              cars_carmanufacturer,
              cars_carmodel
            WHERE
              cars_car.available = True AND
              cars_car.add_to_slider = True AND
              cars_car.under_maintance = False AND
              cars_car.gallery_id = photologue_gallery_photos.gallery_id AND
              cars_car.manufacturer_id = cars_carmanufacturer.id AND
              cars_car.model_id = cars_carmodel.id AND
              photologue_gallery_photos.photo_id = photologue_photo.id''')

    cars = cursor.fetchall()

The solution is temporary, until one of the respected experts says: "Dumbass, is that really how they do it? It's not kosher to write SQL in django, and it's so crooked, ept ...", and of course writes his own super-duper correct code .
UPD
photologue_gallery_photos = this is the table through which the many-to-many relationship goes (photologue_gallery and photologue_photos)

Answer 1

The simplest solution is to add a field to the car with a clear indication of one single photo and put it down at the time the car is saved or the photo is saved to the gallery. Otherwise, you are left to chance, choosing a photo that turns up.
Well, if in the current configuration - try prefetch_related - it will make another fetch to the database, but I'm not sure if it will work on the current scheme.