Mmmm, Parse use Flow, which is a a thing similar to Typescript. Iām not sure in your case if youāre using the original Parse sources that include Flow.
Iām probably not the best to help you with this. It seems like an issue with project configuration, but Iām not sure.
For the User (_User) schema (Other external table schemas are normal), it could be added to the collection even if data is not confined to the schema (the schema strict: true):
Thanks for reply. They are different while seems quite similar. Json-schema is the standard specification in this area to some extent, there are some tool chains already, like:
ā¦
Just some idea: if parse server could adapted to support json-schema, many open source projects could be helpful out of the box to make parse server version 5 to be more stronger and easy to use.
Hi @xeoshow , unique indexes/custom indexes are still not supported.
But, in my company we encountered an issue with the current interface of Parse Indexes, there are too restrictive. So maybe Iāll push a PR to allow a ānon-restrictive modeā to allow a developer to create any indexes without validation or transformation. The goal is to send the index config directly to the DB.
@Moumouls Thanks for kind help.
Actually I met the problem described in this post:
I think maybe the simple solution is to create the unique indexes on the related fields, which should be ārestrictive modeā, otherwise that bug still will happen.
BTW, we have already used the indexes in our schemas similar as below, but it looks like NOT unique index?
indexes: {
tagsIndex: { tags: 1 },
// The special prefix _p_ is used to create indexes on pointer fields
cityPointerIndex: { _p_city: 1 },
tagAndCityIndex: { _p_city: 1, tags: 1 },
},
You can create standard indexes or unique indexes by accessing the adapter directly. I show code for how to do this here:
There are other types of indexes you are not able to create as @Moumouls pointed out, for those, I typically run a script to add them to the DB directly.