Reputation
Top tag
Next privilege 100 Rep.
Edit community wikis
Badges
1 4 18
Impact
~27k people reached

Mar
31
comment “Cannot resolve table name” error when applying MySQL dump to RDS
@RolandoMySQLDBA If I'm not mistaken, bounties are never refunded; but it doesn't matter, I've found the solution to my problem, this is the most important thing! Thanks for your comment anyway, I stumble upon your answers on this website regularly, and they do help a lot.
Mar
31
awarded  Self-Learner
Mar
29
suggested rejected edit on How to check the consistency of tables in mysql
Mar
29
revised “Cannot resolve table name” error when applying MySQL dump to RDS
deleted 3 characters in body
Mar
29
revised “Cannot resolve table name” error when applying MySQL dump to RDS
added 228 characters in body
Mar
29
comment “Cannot resolve table name” error when applying MySQL dump to RDS
@RolandoMySQLDBA My tables are large, so I trimmed down my dump file to give you a small, reproducible example, but this lead me to find out that this was a known bug (see my answer below). So, thank you for putting me on the right track, in some way :)
Mar
29
accepted “Cannot resolve table name” error when applying MySQL dump to RDS
Mar
29
answered “Cannot resolve table name” error when applying MySQL dump to RDS
Mar
29
revised Why does Management Studio add the second alter table “CHECK CONSTRAINT” for a foreign key constraint
Remove thanks
Mar
28
suggested approved edit on Why does Management Studio add the second alter table “CHECK CONSTRAINT” for a foreign key constraint
Mar
28
revised How to troubleshoot ORA-00333 with NOARCHIVELOG mode
Remove thanks
Mar
28
suggested approved edit on How to troubleshoot ORA-00333 with NOARCHIVELOG mode
Mar
28
revised Running pt-table-checksum on a table in different databases
Removed regards
Mar
28
suggested approved edit on Running pt-table-checksum on a table in different databases
Mar
25
awarded  Yearling
Mar
25
asked “Cannot resolve table name” error when applying MySQL dump to RDS
Mar
25
comment What's the risk of keeping a table with row size > 8126 in MySQL 5.7?
The first two are the defaults in MySQL 5.7 indeed. I have tried ROW_FORMAT=DYNAMIC as mentioned in the comments, but that did not help as most of the fields are varchars and not blobs! So I'm stuck with this table in its current state, and with my interrogations.
Mar
24
revised What's the risk of keeping a table with row size > 8126 in MySQL 5.7?
added 9 characters in body
Mar
24
revised MySQL: Row size too large (> 8126)
Removed Please Help
Mar
24
revised What's the risk of keeping a table with row size > 8126 in MySQL 5.7?
edited title