You can have separate workers for each tenant. I'm not sure if that's the "official" way of doing th
You can have separate workers for each tenant. I'm not sure if that's the "official" way of doing things but that's how we're doing it.
/accounts/{account-identifier}/d1/database)WNAM region but I'd prefer Europe DB.prepare('select * from blog').all() But the stored frontmatter is returning json as string instead of automatically parsing it out as json. JSON.parse() or is there any way to do this automatically ? I read somewhere, that libraries like kysley or drizzle does this automatically, but I dont want to add extra layer of code and stick to prepare statements
GLOB should already be limited, as LIKE & GLOB are supposed to be controlled by SQLITE_LIMIT_LIKE_PATTERN_LENGTH which is set to 50.GLOB is limited to 50 bytes as documented for me

/*
SQLite does not support "Changing existing column type" out of the box, we do not generate automatic migration for that, so it has to be done manually
Please refer to: https://www.techonthenet.com/sqlite/tables/alter_table.php
https://www.sqlite.org/lang_altertable.html
https://stackoverflow.com/questions/2083543/modify-a-columns-type-in-sqlite3
Due to that we don't generate migration automatically and it has to be done manually
*/CREATE TABLE blog (
id TEXT PRIMARY KEY,
created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
content_url TEXT,
frontmatter JSON,
slug TEXT UNIQUE,
title TEXT,
website_ref_id TEXT,
FOREIGN KEY (website_ref_id) REFERENCES website(id)
);select id,
content_url,
json(frontmatter) as frontmatter,
slug,
title,
website_ref_id,
created_at
from blogd1.prepare('select * from abc where id in(?,?)').bind(1,2)