fenway

Or using HAVING.

TLDR... what's the gist of the question?

Same way... switch to a join... you have a working example (but use INNER).

Why the GROUP BY??? Remove it.

Not sure what you're asking... but probably yes under certain circumstances. Please provide desired sample output.

I don't understand what's wrong anymore.

Then I like to use "LIMIT 1" to make it obvious. Not sure how you mean... what other way would there be?

Well, you rejected the original solution, which was simply to have one row per TEXT record.... mysql will have no issue handling this.

To make sure innodb in enabled, that your directories are configured correctly, etc.

What else have you tried w.r.t the isamchk command? I'm been re-reading the manpage. 1) Are you sure there's enough free space (at least 2-3 times the file size?) on the temp dir? 2) Do you have a backup of these files? 3) Have you tried to "force" the repair? 4) Have you tried to "safe-recover"? Let's start with these.... you may have done this already, but I just wanted to be sure. There's also this link from an old version of the manual that describes a 4-step process to recovery... has some interesting suggestions re: index file re-creation. Keep me posted! Good luck.

---bringing this discussion back on-line--- Yes, I think it does have to do with the 4GB limit... in fact, you're over it: 4GB = 4294967295! I didn't notice that originally. What OS are you running? Can you run "show table status like ' '" for each table? Take a look at this article; see if you can change max_rows with an ALTER statement as described... it's our best bet right now.

Check the config files....

There is no subquery present...

But that's just the point... there's no "choice"... only Text ID can be in the column list with the other aggregate functions. And I think you mean SUM(CHARLENGHT(`text`))....

If you left join, then any non-null condition that you want to check needs to be in the on clause, not the where clause.

Use code tags next time. That's a strange error for an INSERT... are you sure?

You CANNOT mix * and GROUP BY!!!

I'm assuing there's only one matching row in each subquery? If so, it's fine.

I meant on this forum/board.

What is the output now?

Read this and this "bug". Nothing magical here.

Please post the relevant code on this board... not the file itself. Also, do the mysql queries work?

Careful, though... it has a max_length.

There's a GROUP_CONCAT() function... but there are caveats.