uncheckedScalarInputs One relationship unchecked

Bug description

If we have a table which has two or more relationships, we can’t use both the “connect” method and direct id method. Also ‘create’ relationship won’t work on other relationships

How to reproduce

    return this.prisma.zone.create({
      data: {
        facilityId: record.cityId, // direct
        city: {
          connect: {
            id: record.cityId // using connect
          },
        },
      },
    });

Create

    return this.prisma.zone.create({
      data: {
        facilityId: record.cityId, // direct
        city: {
          create: {
            name: record.city.name, //create
          },
        },
      },
    });

Expected behavior

It should allow both ways for different relationships. Right now with the XOR check its deciding either checked or unchecked input type for the object.

[pantharshit00]

Hey @DregondRahl

This is intentional right now. The problem here is if we allow both cases for each foreign key, there will be too many permutations and input generation will blow exponentially. For example with four foreign keys, we will need to generate 2^4=16 input types.

For now you will need to either choose use one of the syntaxes. My recommendation would be to if you fallback to connect method if you need connect via some other field.

[matthewmueller]

Thanks @pantharshit00, closing. We can re-open if that doesn’t work for you @DregondRahl.