Jump to content

fenway

Staff Alumni
  • Posts

    16,168
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by fenway

  1. The problem is that you upgraded to mysql 5 without reading about how the comma order precedence changed. You can't mix this with JOIN anymore the same way.
  2. Well, let's see the EXPLAIN output of some of your queries.
  3. Simply creating the table won't solve your problem... a missing table likely has missing data.
  4. It will match by whatever you ask it to match.
  5. Yup... but your script might timeout, so be careful.
  6. There are some excellent stickes on this topic, too.
  7. v5.1 has an event scheduler...
  8. I mean joining them in the query, not in the actual tables...
  9. You need version 4.1 to use subqueries, AFAIK.
  10. So you should be able to get all of this back from a single query by joining the relevant tables...
  11. select <column-list> from register_account where id='$afso_userid' union select <column-list> from activity_table But it's very dangerous to do this without explicitly listing the column names in both!!!!!!!
  12. This isn't a mysql question.
  13. It's my.cnf, not my.conf.
  14. This is degerating into a purely php issue -- and it's about to be moved.
  15. Because not all postal codes are number, and phone numbers have meaningful substrings. Since you'll never be able to meaningfully sort by either, there's no point. Because it's very poor w.r.t. performance.
  16. You'll need to LEFT JOIN the products table to the mechanisms table... if products.mechanism_name isn't null, show a link.
  17. You need a while() loop to iterate through the rows.
  18. int(20) doesn't actually do anything... not as far as the data are concerned.
  19. Nothing wrong with leaving them out around numbers, but only if you hard-code the numbers and they never come from user input -- which is why it's just easier to quote everytning.
  20. Quote your variable.
  21. Why not just SELECT task FROM ______ WHERE user='user' And figure out what tasks they completed?
  22. Sounds like a good idea to me.
  23. How did you make this estimate?
  24. Don't store postcodes or phone numbers as INTs. Don't use TEXT fields. And make sure you pick reasonable lengths.
  25. That's very specific.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.