fenway

I meant in terms of scalability... this need not concern you at this stage, you'll just get lost in subjective opinions -- every case is different. Go with InnoDB, and don't use separate databases if you want to share anything. If anything, you can store the users in their own table, and use project prefixes -- or, if you want, separate project DBs and a users DB.

Huh?

"select distinct email, date and group by email" really should be "select email, date and group by email, date". Don't use DISTINCT -- it's evil.

See here..

Yes, but we're talking about variable NAMES, not variable IDENTIFIERS -- so it's only beneficial to the human in question. And it matters even if you're not working on a team -- going back into 5-year-old code and trying to guess what a variable holds is all but impossible. A simple convention will save you hours.

@abamaca -- post your query.

Over 500? How did this random list of IDs get generated?

Try the CSV engine type.

Those sizes are screaming for another table.

Sorry, I don't follow.

You mean trigger into another table, or the same table?

Don't mix DISTINCT and GROUP BY -- that's misleading and error-prone. You can group by both columns.

Your table is just SCREAMING for a UID.

Have you started this project yet? If not, these three shouldn't be your primary concern.

Everything matters -- either it's the SQL statement (a string) or the query handle (an object).

Then you're not storing IPs correctly.

You really should always have a password for root.

Height as an ENUM field? Bad idea. Height as a VARCHAR? Bad idea.

You need to isolate a unique group first, and then join upwards.

Learning SQL is like learning English -- don't bite off more than you can chew.

You should NEVER need to retrieve the password.

Well, you're not supposed to store delimited data when you (a) aren't storing individual elements of an array and (b) need access to an arbitrary element. You're missing some tables. And SUBSTRING_INDEX() can help you if the want the "inside".

Oh, I really like that idea! +1

Covers: Part 1: Using the MySQL Improved Extension, mysqli Part 2: Using the MySQL Extension, mysql Part 3: Using the PDO Extension With MySQL Driver, pdo_mysql Part 4: Using the MySQL Native Driver for PHP, mysqlnd Tutorial is here.

Well, a scalar subquery, that is.