Hi, I have a table that creates profiles based on a memberId. A member can have more than one profile (In case you wonder, the solution has been designed for the data to be not normalized, which is not optimal I know but I have to roll with it). Now before the requirements change occurred I created a document service that worked fine until memberId became non-unique. So my question is, is it possible to call the read() method on a non-unique key field in a table? Is it possible to change the service for fields that do not have an index (not recommended I am ware of that, I am just curious)? Or should I create a custom service instead? I appreciate your time. Thanks, Daniel
↧