Option Set or Data Type | performance

francochapa01 · 2022-11-14T01:29:33.343Z

Hi!
I’m building an app where the users can give their opinion on movies. The users will be able to see all the opinions related to that movie.

I’m defining the database structure. I read that option set are faster for searching. So, my doubt comes to what’s best… making a data type ‘Movies’ (that has different data fields); or making an option set ‘Movies’ (that has different attributes).

Is more easy to make with data types (because I can import /export csv; and because there are a lot of movies); but how much slow it will be when searching (comparing to option sets)?

keith · 2022-11-14T01:38:22.807Z

This will basically HAVE to be a Thing (custom datatype).

francochapa01 · 2022-11-14T01:44:21.828Z

Yes, that’s waht I imagine, but I will not have bad performance when searching all the opinions on each movie?

luke2 · 2022-11-14T09:22:56.607Z

The performance will be fine, managing Movies as an option set would be a bad idea and would really lock you in, there not really made for that.

Just ensure that with the ‘Opinions/Reviews’ this is its own data type with a reference data object field ‘Movie’ rather than having a list of ‘Opinions/Reviews’ on a Movie data type, as once you get into the 1k mark, performance takes a hit and initial search + filtering will run better initially server side.

francochapa01 · 2022-11-14T09:49:11.508Z

Thanks for your answer! I appreciate it