Hitting SQLITE_TOOBIG when trying to deploy via nuxthub

[acidjazz]

I think this issue belongs here possibly

error i'm getting:

Run nuxt-hub/action@v1
Processing database migrations...
Found 0 applied database migrations
Applying database migration 0000_purple_omega_flight...
Applied database migration 0000_purple_omega_flight
1 database migrations applied
Applying 5 database queries...
Applying database query content-database-001...
Error: Failed to query database: statement too long: SQLITE_TOOBIG
Error: Failed to apply database query content-database-001: Failed to query database: statement too long: SQLITE_TOOBIG

[acidjazz]

update: SQLITE_TOOBIG is a sqlite error - not a D1 limit

tried some PR's to attempt to change SLICE_SIZE in src/utils/collection.ts to a smaller size, even at 20k I'm still getting this error.

while I still get the error for adjusting that parameter, I'm seeing more inserts happen in one of the content tables as the deploy is attempted. not sure if that means much, or if i'm in the right place when attempting to fix this.

here's a bit more context on my content/:

total of 321 markdown files, here are some folder sizes

❯ du -sh *
336K	advisories
1.3M	blog
136K	events
 88K	news
132K	pages
176K	press

here are some of the largest sizes in blog/

❯ du -sh * | sort -hr
 36K	xiongmai-iot-exploitation.md
 36K	confluence-dreams-of-shells.md
 36K	bigant-cve-2025-0364.md
 28K	new-cve-2022-1388.md
 24K	zyxel-telnet-vulns.md
 24K	openfire-cve-2023-32315.md
 24K	moobot-uses-fake-vulnerability.md
 24K	mikrotik-foisted-revisited.md
 24K	2022-missing-kev-report.md

[acidjazz]

Update: I found the culprit that is triggering this d1 error and will be able to whip up a reproduction when I get more time - should help target what needs to be tweaked - essentially its heavy metadata in content config.

[acidjazz]

Update: I think this is happening when we use rawbody https://content.nuxt.com/docs/advanced/raw-content

[MauPalantir]

@acidjazz hey, do you have an idea of how to circumvent this issue? I have a site with lots of content when I started migrating and added the first 1000 content entries I started getting this error. I don't use raw content.