Add option to use BigInt in autoincrement idField

[MurzNN]

Now for autoincrement idField only Integer field type is used, which sometimes is not enough.

In this PR I've implemented an option "useBigInt" in idField configuration, that switches to use BigInt as idField in database. Here is an example how to enable this feature:

    db: {
      idField: {
        kind: 'autoincrement',
        useBigInt: true,
      }
    }

Related discussion: #6969

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/8yuTCNpCzaTZTQz9iLbSCZLzf3Z5
✅ Preview: https://keystone-next-docs-git-fork-murznn-idfield-bigint-keystonejs.vercel.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit d4f4661:

Sandbox	Source
@keystone-6/sandbox	Configuration

[changeset-bot]

🦋 Changeset detected

Latest commit: d4f4661

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages

Name	Type
@keystone-6/core	Minor
@keystone-6/auth	Major
@keystone-6/cloudinary	Major
@keystone-6/fields-document	Major
@keystone-6/session-store-redis	Major
@keystone-6/example-auth	Patch
@keystone-6/examples-app-basic	Patch
@keystone-6/example-ecommerce	Patch
@keystone-6/example-graphql-api-endpoint	Patch
@keystone-6/example-roles	Patch
@keystone-6/example-testing	Patch
@keystone-6/example-with-auth	Patch
@keystone-6/sandbox	Patch
@keystone-6/website	Patch
@keystone-6/example-document-field	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[dcousens]

Awesome work on this @MurzNN!
We haven't forgotten about this, we simply took a while to come around the mountain.

Thinking about it, I think we would want to add a db.idField.type as the discriminating factor instead of useBigInt.

For example

db: {
  idField: {
    kind: 'autoincrement',
    type: 'Int' | 'BigInt' // the underlying Prisma type, the default is 'Int' when `kind: 'autoincrement'`
  }
}

This will then be aligned with other advanced changes we intend to add, for example with our other work

• Add support for MySQL #7538

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	Jun 24, 2022 at 3:25AM (UTC)

[MurzNN]

@dcousens yeah, adding type will simplify the whole construction, but will require more changes in core, but seems it almost implemented already, thanks!