Update astro-db.mdx

[wlai-lp]

Description (required)

add some missing details to make the tutorial more fluid. if you follow the tutorial, at this point, your comment table has author and content columns. The seed script is going to fail because it's missing data in the author table and the Comment table does not have body column

Related issues & labels (optional)

• Closes #
• Suggested label:

[vercel]

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

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Jun 11, 2024 9:09am

[astrobot-houston]

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any broken links you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale	File	Note
en	guides/astro-db.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[sarah11918]

Hi @wlai-lp ! Thank you for pointing this out! However, these two examples are not meant to follow each other. This is not a tutorial where you complete every step in order, but just a very minimal example of each process. In fact, none of the examples necessarily work with each other, so that's entirely expected!

I do think your changes are helpful though, for people who are treating it like a tutorial! I will just make a minor change as we like to try to be representative of our global audience when adding new names in our code examples. Thank you again for this contribution, and I am happy to welcome you to Team Docs! 🥳

[sarah11918]

NOTE: Not merging until we figure out why the deploy build is failing, just to be safe! 😄 (Probably not related to this PR, but want to make sure our builds are working first before merging new PRs)