A related bug #859 was fixed in release v1.0.12 that had to do with unique indexes. All the problems with indexing should be resolved now. @andwrobs, this covers the bug you pointed out in the demo.

We also decided to not do anything in the short term regarding the idea to add a payload script for building indexes. The reason for this decision is that:

1. The functionality is already a part of mongoose with diffIndexes() and ensureIndexes() which can be called on the Model. See https://mongoosejs.com/docs/api.html#model_Model-diffIndexes and https://mongoosejs.com/docs/api.html#model_Model-ensureIndexes
2. It could be built into Payload, but it belongs under a subset of features that would essentially be a migration tool that is more robust.

I’m going to close this issue for now because I think we have addressed everything in the thread. Please open any new issues or discussions for new features as needed. Thanks everyone who contributed!

Hi Dan,

Great suggestion of --dry-run , i think in dev ENV/debug mode it should list the indexes that are miss match or need to be created and a message/command, suggesting a flag to be added for auto index creation , it must also look up total records count for the respective index like up till 1000 and also suggest the performance issue while enabling the index flag.

i am still new to Node/JS so its up for suggestion and discussion .

Lastly i must say, i am testing Payload for just 1 day , i am fairly impressed with the possibility it offers, great work!

Hey @geminigeek, were you able to store unique text in the collection? If so, could you please enlighten me with the same.

we tried and it works with adding option localized: false in the text field. we use mongodb atlas as a source of database