Currently if we want to access Database from Client Side, We have following "Access Rights" Options to be set for a particular connection.
1) CanLoadByKeys
2) CanLoadByIndexes
3) CanCreate
4) CanSave
5) CanDelete
6) Full Creator Rights
Also, I can see for PlayerObject, documentation talks about the fact that particular player can read/write only his/her data..
PlayerObjects
The absolutely most common use-case for BigDB is to store data on a per-player basis, and making sure that one player cannot read or modify the data of another player.
Now i have two Questions..
1) In PlayerObject database, I tried from Server side code and I can read or modify the data of another player. So, now If we assume the above statement is made for client side code then I don't see any Settings in Connections page where I can set PlayerObject to "Read/Write only its own data"..
2) Is it possible to introduce a new "Access Rights" Options (client side) called as "Read Only Own Data" and "Write Only Own Data".. Which can be used with PlayerObjects as well as other tables...
I understand, this might be too much of work at your end, but the reason I am asking for this is that this can give increased security at client side, and can avoid connecting to SERVICEROOM at all (or reduce dependency in many cases), which I am currently planning to use only for data fetching/Writing..
Thanks,
Aseem