Updates across docs and blog for new terminology for DB + string

[atharvadeosthale]

No description provided.

[greptile-apps]

Greptile Summary

This PR performs a large-scale terminology update across 22 blog posts and 1 documentation page, renaming Appwrite Database concepts from NoSQL-style vocabulary (collection, document, Databases, String) to relational-style vocabulary (table, row, TablesDB, varchar/text). The changes are consistent across all files and all supported SDK languages (JavaScript, PHP, Python, Swift, Ruby, C#, Dart, Flutter).

• All SDK method names updated: createDocument→createRow, listDocuments→listRows, updateDocument→updateRow, deleteDocument→deleteRow, getDocument→getRow (and bulk variants)
• Databases class replaced with TablesDB across all code samples and all SDK languages
• API call signatures updated from positional arguments to named object parameters matching the new API contract
• String attribute type replaced with varchar / text throughout
• Environment variables renamed (e.g. PUBLIC_APPWRITE_COLLECTION_ID → PUBLIC_APPWRITE_TABLE_ID) consistently
• A pre-existing duplicate code-fence in how-to-optimize-your-appwrite-project was incidentally fixed
• One P2 style concern: offline-first-journal line 242 uses collectionId: appwriteConfig.tableId — the key collectionId is mandated by the third-party RxDB Appwrite plugin and was intentionally left unchanged, but the value now references the newly renamed appwriteConfig.tableId, creating confusing mixed terminology for readers

Confidence Score: 5/5

Safe to merge; all changes are documentation and blog content updates with no production runtime code affected

The single finding is a P2 style concern in a third-party RxDB plugin call where the key name is dictated by an external API contract. All Appwrite SDK method calls, parameter names, env variable names, and prose are consistently and correctly updated across all 29 changed files.

src/routes/blog/post/offline-first-journal/+page.markdoc line 242 deserves an inline clarifying comment; all other files are clean

Important Files Changed

Filename	Overview
src/routes/docs/products/databases/timestamp-overrides/+page.markdoc	Comprehensive terminology update across all SDK examples (JS, PHP, Swift, Python, Ruby, C#, Dart): Databases→TablesDB, collectionId→tableId, documentId→rowId, and all method names
src/routes/blog/post/offline-first-journal/+page.markdoc	Terminology updated throughout; one confusing mixed-terminology at line 242 where the RxDB plugin key collectionId was correctly kept but the value now references appwriteConfig.tableId
src/routes/blog/post/announcing-bulk-api/+page.markdoc	Correctly updated to TablesDB with createRows, updateRows, deleteRows, upsertRows and tableId; call signature migrated from positional to named object params
src/routes/blog/post/appwrite-realtime-for-flutter/+page.markdoc	Flutter tutorial updated to TablesDB, listRows, createRow, deleteRow, res.rows; new Channel helper used for Realtime subscription; UI steps updated to 'Create table'
src/routes/blog/post/understand-data-queries/+page.markdoc	listDocuments positional-arg calls correctly converted to tablesDB.listRows named-object params for OR, AND, CONTAINS examples
src/routes/blog/post/how-to-optimize-your-appwrite-project/+page.markdoc	listDocuments replaced with listRows throughout; pre-existing duplicate code-fence accidentally fixed; doc link updated to /tables#listRows
src/routes/blog/post/ai-crystal-ball/+page.markdoc	Full update to TablesDB API (getRow, createRow), env vars renamed to TABLE_ID variants, config object and prose updated
src/routes/blog/post/best-pagination-technique/+page.markdoc	Pagination code examples migrated from Databases.listDocuments positional args to TablesDB.listRows named-object params
src/routes/blog/post/announcing-auto-increment-support/+page.markdoc	TablesDB and listRows updated consistently; $sequence feature description updated to reference rows
src/routes/blog/post/announcing-database-reads-and-writes-pricing/+page.markdoc	Pricing descriptions updated to getRow/listRows/createRow/updateRow/deleteRow; per-row counting explanation updated
src/routes/(marketing)/(components)/(ai-animations)/skills.svelte	Single skill name updated from createDocument to createRow in marketing animation component
src/routes/blog/post/introducing-new-database-operators/+page.markdoc	Operator examples updated to tablesDB.listRows with tableId parameter; contains and or examples unaffected
src/routes/blog/post/simplify-your-data-management-with-relationships/+page.markdoc	Relationships blog updated with table/row terminology throughout
src/routes/blog/post/track-document-order-with-sequence/+page.markdoc	$sequence feature blog updated with row/table terminology and TablesDB API

_{Reviews (1): Last reviewed commit: "more blogs" | Re-trigger Greptile}

[greptile-apps]

Mixed old/new terminology in replicateAppwrite() call

The key collectionId retains the old Appwrite terminology while its value now reads from appwriteConfig.tableId — a config field renamed earlier in the tutorial. The code is functionally correct because the RxDB Appwrite replication plugin still expects collectionId as its parameter key (third-party API contract), but the juxtaposition is confusing for readers: they may think the access path is wrong, or that they should define a collectionId key in their config instead of tableId.

A brief inline comment would resolve the ambiguity:

Suggested change

	collectionId: appwriteConfig.tableId,
	collectionId: appwriteConfig.tableId, // 'collectionId' is the parameter name required by the RxDB Appwrite plugin

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}