Is it possible to create different ParseUser
implementations, each one with its own fields? For example, we have a Student
and a Company
classes extending ParseUser
and we want to separate the Student's specific fields from Company's ones, but when I try to persist a new Student or a new Company it will work only if both student and company's specific fields are modeled inside _User class. Can I have two custom objects, extending the ParseUser
class in order to make them able to use the built-in Login function?
How about three tables, User, Student, and Company. Student and Company each have a pointer to User. That allows you to use parse authentication, and separate the different types of data, at the expense of complicating the queries somewhat. If you don't want to do that, Thellimist's solution will also work.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.