Update 125-creating-the-prisma-schema.mdx

[Nditah]

Fix: Update Post Schema: Change user to author and userId to authorId

Describe this PR

Changes

What issue does this fix?

Any other relevant information

[netlify]

✔️ Deploy Preview for prisma2-docs ready!
Built without sensitive environment variables

🔨 Explore the source changes: 2c7e5b3

🔍 Inspect the deploy log: https://app.netlify.com/sites/prisma2-docs/deploys/6228a2cd77bb4f0008ec45a5

😎 Browse the preview: https://deploy-preview-2960--prisma2-docs.netlify.app

[janpio]

Why this change? Is the current version broken? Is this "just" a question of style?

[Nditah]

Sir, the reason for the change is *Logical Consistency.* The Article in at least 3 places discusses the schema cited *author* and *authorId*. https://www.prisma.io/docs/getting-started/setup-prisma/start-from-scratch/mongodb/querying-the-database-typescript-mongodb Thank you.

…

On Wed, 9 Mar 2022 at 15:49, Jan Piotrowski ***@***.***> wrote: Why this change? Is the current version broken? Is this "just" a question of style? — Reply to this email directly, view it on GitHub <#2960 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHYKX5AGLFEBEYFRUEYCSEDU7C27ZANCNFSM5QJOJKTQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tanberry]

Thanks @Nditah for raising this question.... I'm not sure that changing user to author is the best way to demonstrate the relation between those two. This relation is explained here in our docs....

@matthewmueller can you take a look at this and share your opinion, please?

[tanberry]

Let's go ahead and merge this, thanks @Nditah , and I'll open a new Issue for going through that whole set of docs and making them more consistent about userID versus authorID.