Add new string types to tables section of docs

[atharvadeosthale]

Summary by CodeRabbit

• Documentation
  • Updated Columns docs to add varchar, text, mediumtext, and longtext with usage and limits.
  • Replaced occurrences of the deprecated string type with varchar in SDK examples and sample code across languages.
  • Added a deprecation notice for the string column type and updated examples to reflect the new preferred types.

[coderabbitai]

Walkthrough

This PR updates a Markdoc documentation page for database table column types: it replaces uses of the string column type with varchar across multiple language SDK examples, adds four explicit text types (varchar, text, mediumtext, longtext) with descriptive usage, and introduces a deprecation notice for string. The Columns documentation table and examples were updated to reflect these types. No runtime or control-flow behavior was changed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title accurately summarizes the main change: adding new string types (varchar, text, mediumtext, longtext) to the tables documentation section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch new-string-types

---

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: 1

🤖 Fix all issues with AI agents

In `@src/routes/docs/products/databases/tables/`+page.markdoc:
- Around line 1245-1249: Update the doc to stop showing deprecated `string` in
examples and clarify migration rules: change any example columns using `type:
'string'` to a recommended replacement such as `type: 'varchar'` (or
`text`/`mediumtext`/`longtext` as appropriate) and edit the "Migrating from
string columns" info block to state explicitly whether the migration chooses the
resulting text type based on the declared column size (e.g., the `size` option
you specify) versus the size of existing row data—if the implementation uses the
declared size, say "based on the declared size (`size` option)"; if it inspects
actual data, say "based on the maximum size of existing data"—so consumers and
examples (e.g., snippets that previously used `type: 'string'`) are consistent
with the guidance.

🧹 Nitpick comments (1)

src/routes/docs/products/databases/tables/+page.markdoc (1)

1227-1232: Clarify how varchar vs text should be chosen.

Both rows show the same 16,383-character limit and near-identical descriptions (Line 1229–1232), which makes the selection criteria unclear. Consider adding a short note distinguishing intended usage (e.g., varchar requires a size, text is for longer prose), or adjust limits if they differ.