From 83e9f537fe0157eb237ce4a197ac98da12c3362a Mon Sep 17 00:00:00 2001 From: asonix Date: Tue, 25 Jul 2023 21:14:11 -0500 Subject: [PATCH] Serizlie --- docs/postgres-planning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/postgres-planning.md b/docs/postgres-planning.md index 16344a6..61ff42c 100644 --- a/docs/postgres-planning.md +++ b/docs/postgres-planning.md @@ -130,7 +130,7 @@ CREATE TABLE details ( ### QueueRepo This is going to be the troublesome table. It represents jobs that will be processed. Jobs are pushed as Bytes, but at a higher level are actually JSON strings. The QueueRepo API could be updated -to take `T: Serizlie` as input rather than bytes, and then we can store it as JSONB. With the +to take `T: Serialize` as input rather than bytes, and then we can store it as JSONB. With the current API, the repo doesn't need to know the shape of a job, and maybe that is a benefit. We should take care in the future not to query on the contents of the job.