Note that there are some explanatory texts on larger screens.

plurals
  1. USRageD
    primarykey
    data
    text
    plurals
    1. COWhat is the question? Are you wondering about database architecture, or actually harvesting and storing the information? I would recommend a large team to harvest and store the information (since you will most likely have to do much of it by hand), but the structure should not be too complicated. Over-simplified you only need about 7 fields: fields for a unique identifier, movie title, movie director, actors, pictures, information, date. Good luck.
      singulars
    2. COOliver is correct below. There probably isn't a much better solution (if I am understanding correctly) than using a session or cookie to store the data. In any case, you need to store that data somewhere. Depending on your motives, another potential solution would be to simply store the information to the database as you go. Then run a cron to check status and if older than a day or so purge results which are incomplete. But again, to keep things organized you would probably need a recurring post and/or session and error checking as these things can be spoofed in any case.
      singulars
    3. CO@Daniel: Based off of what Steve and Niall said, you must remember your program's structure and hierarchy. E.g. <iostream> is included in something.h and something.h is included in main.cpp but not something_else.cpp. Then iostream is effectively included in any file where something.h is included (in this case main.cpp) and not those files which do not (in this case something_else.cpp). So if you had no reason to include something.h into something_else.cpp, you would simply re-include <iostream> if you needed the standard functionality in there as well. Good luck!
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload