Chinoman10 Comments - Answer Overflow

Chinoman10

•Created by yevgen on 10/21/2024 in #vectorize

there is no support for contains. We are

Thanks for getting back to me 🙏 I've gone ahead and picked the filter which I believe would filter out most of the results and I run a 2nd query with that filter on... I'll write some comments in the code that specify how we should change it whenever the $nin operator becomes available. (actually, in theory, we should be able to have both codes live... we simply check if the operator exists, if it does, great, it 'auto-upgrades', and if not (until it happens) it uses the legacy system).

4 replies

CDCloudflare Developers

•Created by yevgen on 10/21/2024 in #vectorize

there is no support for contains. We are

Hello yevgen, it's great news that this is coming. How could I achieve a similar result today for 'not in a specified array'?

[
  { "metaId": { "$ne": "id1" } },
  { "metaId": { "$ne": "id2" } },
  { "metaId": { "$ne": "id3" } }
]

[
  { "metaId": { "$ne": "id1" } },
  { "metaId": { "$ne": "id2" } },
  { "metaId": { "$ne": "id3" } }
]

{
 "metaId": { "$ne": "id1" },
 "metaId": { "$ne": "id2" },
 "metaId": { "$ne": "id3" }
}

{
 "metaId": { "$ne": "id1" },
 "metaId": { "$ne": "id2" },
 "metaId": { "$ne": "id3" }
}

{
 "metaId": { "$ne": ["id1","id2","id3"] }
}

{
 "metaId": { "$ne": ["id1","id2","id3"] }
}

Because the 2nd isn't valid JSON (object with non-unique keys), but the docs don't have an example with an array (so I dunno if it's possible). And the 3rd one seems like what you guys are building, but probably isn't supported with the '$ne' operator. Edit: I've confirmed with the worker.types, indeed the filters don't support string[] 😭

4 replies

CDCloudflare Developers

•Created by Chinoman10 on 7/27/2024 in #durable-objects