Catch up wih the Appery.io community on our forum. Here you'll find information on the lastest questions and issues Appery.io developers are discussing.
https://forum.appery.io/
That isn't efficient since the Collection is being accessed twice instead of once. It's also not 100% effective. Between the time of reading and adding, a record could be added with the same key.
I have added this feature to our planning list.
Unique indexes would definitely help simplify some app logic and minimize queries for checking against records that must be unique. Any update as to where this falls on the planning list?
I'll check with our dev. team.
We are planning to add this in early summer.
I would also like compound uniqe indexes because without these indexes we cannot be sure if another user is storing the Exact same values in another
row almost simultaniously. To avoid this Logic on app or in servercode cannot prevent this because from the moment you have confirmed that this record does not exist another user can save the same record just before you are saving the same record.
Hi Jesper,
This will be added in the end of July.