Would it be possible to find out the maximum lengths of things like ID, title, etc so that when entering this info into a database (the TOS says during the user session or 24h, storage is okay) I'll know the correct data type?
I'll check to see if I can provide a better database schema, but for now, here's some general guidelines that should be helpful:
Movie IDs (also used for TVs and pretty much everything else) are always numeric, and since there are 100K movies, you probably want a long value.
Movie titles can be fairly lengthy, but feel free to trim them down to what makes most sense. (I don't think there are a lot of movies with names like "A Funny Thing Happened on the Way to the Forum; Part 3; Hermes Does the Electric Boogaloo".)
Synopses should probably be "blobs" since they'll contain extended characters and elements of markup.
Etags can vary a bit, I'd suggest a 64 character string for those.
Most of the rest of the content should be either self explainatory (e.g. "date") or strings.
Again, these are obviously rough guidelines. I'll have to see if I can get a better schema for this, but understand that things change for us as well. It's always best to try and pick the most flexible way to store data you can (e.g. stuff everything into blobs indexed by title and genre or movieid)
Would it be possible to find out the maximum lengths of things like ID, title, etc so that when entering this info into a database (the TOS says during the user session or 24h, storage is okay) I'll know the correct data type?
Thanks!
Message edited by Kallahar 3 years ago
JR Conlin – 3 years ago
I'll check to see if I can provide a better database schema, but for now, here's some general guidelines that should be helpful:
Movie IDs (also used for TVs and pretty much everything else) are always numeric, and since there are 100K movies, you probably want a long value.
Movie titles can be fairly lengthy, but feel free to trim them down to what makes most sense. (I don't think there are a lot of movies with names like "A Funny Thing Happened on the Way to the Forum; Part 3; Hermes Does the Electric Boogaloo".)
Synopses should probably be "blobs" since they'll contain extended characters and elements of markup.
Etags can vary a bit, I'd suggest a 64 character string for those.
Most of the rest of the content should be either self explainatory (e.g. "date") or strings.
Again, these are obviously rough guidelines. I'll have to see if I can get a better schema for this, but understand that things change for us as well. It's always best to try and pick the most flexible way to store data you can (e.g. stuff everything into blobs indexed by title and genre or movieid)
JR Conlin – 3 years ago
Quick bit of clarification courtesy of Priya:
the ID we use in the API is a URL, therefore you're going to need something capable of storing such.