fenway

You're limiting yourself to just one level of nesting.

The DECIMAL column type must be one of the options -- I've always used alter statements. As for linking them together, you'll need 3 tables -- colors, cars, and the relation table. Simply store a uid tuple in the latter.

No-one is going to download your code -- find the relevant section that pertains to your issue and post it in code blocks.

Then get 8 random ones, union in the one you really want, and then throw out one of the original 8 if necessary.

Change FROM tplss_seasons S, tplss_seasonnames SE to FROM (tplss_seasons S, tplss_seasonnames SE)

Which one?

Well, something has to run code on a schedule -- either mysql or the kernel, your choice.

I find that hard to believe.

That's not mysql.

The "simplest" method is to keep a user-defined variable, which you reset per "group", and simply filter out the rows once you've hit your "limit" -- 2. Of course, by "simplest " I mean easiest to type, not most efficient. If you want the latter, you'll need to forgo examining each record, and use an derived table to get the N-most per group (and dealing with the edge case of there not being N rows), and then join that up the chain.

I mean why can't you script just check -- why maintain a flag that's always out of date?

That's blank, not null.

I don't understand what you're trying to do.

Then you'll need to get a 7-day unique version -- you can't just sum across the days.

Why can't you just check?

This has been covered many times on these forums -- a simple search should reveal the relevant threads.

Sorry, I don't follow.

1. store proper DECIMAL fields, format on output only. 2. use a many-to-many relation table.

That's not correct...

No, not all the code -- just the relevant section.

What's "it"?

Why doesn't "tbl_Combat" have an index on TargetID.

If you want the GROUP_CONCAT() expression to remove duplicates, use the DISTINCT modifier -- the refman covers the syntax.

I'm always wary of sharing tables within a DB that have nothing to do with one another -- you can leave your CMS code alone, use the same table names, etc., but have a different DB from each customer.

Sounds like you just want to dump these rows into a table with an auto-increment field.