Full schema

[LauraDuRy]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• Documentation
  • Added a blog post and changelog entry announcing Full Schema Creation for Appwrite Databases, describing atomic, synchronous table provisioning and all-or-nothing behavior.
  • Updated an author profile (role and Twitter handle) on the site.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• static/images/blog/full-schema.png is excluded by !**/*.png

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

A new blog post was added at src/routes/blog/post/announcing-full-schema-creation/+page.markdoc containing front matter and a full article describing the "Full Schema Creation" feature for Appwrite Databases. A changelog entry was added at src/routes/changelog/(entries)/2025-12-30 documenting the same feature with front matter and a summary. An author page at src/routes/blog/author/aditya-oberai/+page.markdoc was updated to change the role (Developer Advocate -> Developer Relations Lead) and to update the twitter URL. All changes are content/metadata only; no code or runtime behavior was modified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Full schema' is vague and overly generic. It lacks specificity about what the change does (e.g., is it adding, creating, or documenting full schema functionality?) and doesn't clearly convey the main purpose of the PR.	Use a more descriptive title that clarifies the action and context, such as 'Add Full Schema Creation feature announcement and changelog entry' or 'Document Full Schema Creation for Appwrite Databases'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5e20f60 and 67e7bd5.

⛔ Files ignored due to path filters (1)

• static/images/blog/full-schema.png is excluded by !**/*.png

📒 Files selected for processing (2)

• src/routes/blog/post/announcing-full-schema-creation/+page.markdoc
• src/routes/changelog/(entries)/2025-12-29

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: build
• GitHub Check: assets
• GitHub Check: tests

🔇 Additional comments (1)

src/routes/changelog/(entries)/2025-12-29 (1)

1-14: LGTM: Changelog entry is clear and well-structured.

The changelog entry effectively summarizes the Full Schema Creation feature with clear, concise language and appropriate metadata.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Fix the date inconsistency.

The blog post date is set to 2024-12-12, but the corresponding changelog entry uses 2025-12-29. These dates are over a year apart, which will cause chronological ordering issues and user confusion.

Verify which date is correct and update accordingly. Most likely this should be 2025-12-12 to align with the changelog month.

🔎 Proposed fix

-date: 2024-12-12
+date: 2025-12-12

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	date: 2024-12-12
	date: 2025-12-12

🤖 Prompt for AI Agents

In src/routes/blog/post/announcing-full-schema-creation/+page.markdoc around
line 5, the frontmatter date is 2024-12-12 but the changelog uses 2025-12-29;
update the blog post date to the correct year to match the changelog (most
likely change the date to 2025-12-12), or confirm the authoritative date and
make both the post frontmatter and the changelog consistent; ensure the format
remains YYYY-MM-DD.

[adityaoberai]

@LauraDuRy it would also be good to add a code example here

We can use this:

const table = await tablesDB.createTable({
    databaseId: 'contacts_db',
    tableId: 'contacts',
    name: 'Contacts',
    columns: [
        {
            key: 'email',
            type: 'email',
            required: true
        },
        {
            key: 'name',
            type: 'string',
            size: 255,
            required: true
        },
        {
            key: 'is_active',
            type: 'boolean',
            required: true
        },
    ],
    indexes: [
        {
            key: 'idx_email',
            type: 'unique',
            attributes: ['email']
        }
    ]
});

[adityaoberai]

Suggested change

	- [Announcing API for spatial columns: Build scalable location-aware apps with ease](https://appwrite.io/blog/post/announcing-spatial-columns)
	- [Announcing an improved Appwrite Databases experience. A completely new look and feel](https://appwrite.io/blog/post/announcing-appwrite-databases-new-ui)
	- [Announcing Atomic numeric operations: Safe, server-side increments and decrements](https://appwrite.io/blog/post/announcing-atomic-numeric-operations)
	- [Announcing API for spatial columns: Build scalable location-aware apps with ease](/blog/post/announcing-spatial-columns)
	- [Announcing an improved Appwrite Databases experience. A completely new look and feel](/blog/post/announcing-appwrite-databases-new-ui)
	- [Announcing Atomic numeric operations: Safe, server-side increments and decrements](/blog/post/announcing-atomic-numeric-operations)

[adityaoberai]

@LauraDuRy the date is incorrect

[adityaoberai]

Suggested change

	title: Announcing Full Schema Creation: Provision complete tables in one atomic call
	title: "Announcing Full Schema Creation: Provision complete tables in one atomic call"