Make Combined Milestones optional

Given that some users only run one project, they get two posts under this scenario..

sanity check
if (num_projects!=1)
{ run_combined(); }

Doesn't work like that..

It's a single sql statement to find all 'unposted' milestones across the users. I'd have to run a separate sql statement on each milestone found to check for distinct(proj) in the user table which would be somewhat inefficient. Unless I maintained counts which is just another layer to consider.

Far better to allow the user to choose.

Is it not possible to do this check when they first allow the app?
I mean do a row count on the number returned when you do the sql WHERE cpid='$thecpidtheyentered'; ? or is across multiple tables?

And what if they subsequently added another project ?

if they add a new project since this would add a new record. It should be possible to check if they are using the "boinc milestones" app if so check if "combined milestones" is "flagged" as "N" (i.e 1 project) and flag it as "Y" - more than 1....
Yes?

Not really no. We don't do any kind of checks at all for people adding new projects. They just go in as extra records for that project and the indexes handle it via the CPID.

We'd have to have a whole new level of checking on each and every insert to the user table (and that's not even considering split CPID's and the like)

Or an overnight run adding data using a group function so that we held (num_projects) for each cpid.

Even given all of that, what if a user was in 5 projects and wanted to see milestones from them, but not combined milestones?

I think it's much simpler to let the choice be on them.. default YES.

Bok

Yeah I suppose there is that :D

So, are there any developments on this? This is something that has always bothered me about the app. It'd be great to have the option to disable the combined milesones post.

Not really, Facebook has made it more and more difficult to control the app and now insist on every app using SSL which means a costly certificate and a static IP, so to make any changes to the frontend now is going to take quite a bit of work.

I'd certainly like to, but I need to get around those challenges first unfortunately..