isRequired on a field with knex adapter throws errors during back link updates

[jesstelford]

The back linking process for a to-single field uses a brute-force approach right now where it forces the linked field to null, then immediately after sets it to the id.

But if you've got isRequired set, knex will throw an error during the first phase of the back linking.

[stale]

It looks like you haven't had a response in over 3 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contributions. :)

[singhArmani]

@jesstelford @MadeByMike: While trying the following keystone config (with knex) on my macOS and with chrome browser:

const keystone = new Keystone({
  name: 'Keystone To-Do List',
  adapter: new Adapter({ dropDatabase: true }),
});

keystone.createList('Todo', {
  schemaDoc: 'A list of things which need to be done',
  fields: {
    name: { type: Text, schemaDoc: 'This is the thing you need to do', isRequired: true },
    createdBy: { type: Relationship, ref: 'User', isRequired: true },
  },
});

keystone.createList('User', {
  schemaDoc: 'user who owns the todo',
  fields: {
    name: { type: Text, isRequired: true },
  },
});

I wasn't able to reproduce this bug. It seems to be fixed.
Closing it now :)

[MadeByMike]

Fixed by Tim \o/