feat: Support bigint and UUID pagination identifiers

[aXenDeveloper]

Summary

• allow primaryCursor to use integer, bigint, or UUID columns
• preserve bigint precision by storing identifiers as decimal strings in opaque cursors
• validate UUIDs and PostgreSQL bigint bounds before building SQL predicates
• support mixed tuples such as a bigint order column with a UUID tiebreaker
• document the supported identifier types and correct the pagination projection example

Verification

• pnpm --filter @vitnode/core test — 6,164 tests passed
• pnpm --filter @vitnode/core test:types — 315 type tests passed, no type errors
• pnpm --filter @vitnode/core exec tsc -p tsconfig.json --noEmit
• targeted ESLint checks passed

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
vitnode-prod	Ready	Preview	Sep 1, 2026 7:59pm UTC

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 853274ceb3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use the current Drizzle column helper

With the repository's pinned Drizzle v1 release, getTableColumns was renamed to getColumns; the live cron route already imports and calls getColumns in packages/vitnode/src/api/modules/admin/advanced/cron/routes/get.route.ts. Anyone copying this newly updated basic example will therefore get a missing-export error before reaching the pagination code, so replace both getTableColumns references with getColumns.

Useful? React with 👍 / 👎.