Interesting. I could create e.g. "61d8e3w_insert_cached_href_0_request" and "618g3w_insert_cached_href_0_request", but I got the same kind of error as you for your exact table name.
It appears the problem is the "e" character - my guess is that mysql starts to parse "618e3" as a float, and it cannot backtrack from there. This is not according to the manual, so I think it's clearly a mysql bug. I suggest you report it to them. Maybe we can make a workaround for this by replacing the "e" with "x" or something in this particular case. Assuming mysql always had this bug then there will be no working tables with such names, so it wouldn't be a compat problem. Thomas Gusenleitner <[email protected]> wrote: > for example making a select on a table results in a error message like this > > "While running SELECT url, fetch_interval, fresh_time, ttl, timeout, > time_of_day, next_fetch, latest_request FROM > 618e3w_insert_cached_href_0_request : big_query(): Query "SELECT url, > fetch_interval, fresh_time, ttl, timeout, time_of_day, next_fetch, > latest_request FROM 618e3w_insert_cached_href_0_request " failed (You have an > error in your SQL syntax; check the manual that corresponds to your MySQL > server version for the right syntax to use near > '618e3w_insert_cached_href_0_request' at line 1)" > > this also happens with creates, inserts, deletes and so on > > i use mysql 5.0.77
