You can also create a 'merge' table (a collecition of identical MyIsam tables). But currently we do not support MERGE in SQLyog GUI. Unless you need to use full-text indexes (or spatial datatypes) using InnoDB is the simplest solution.
You should *really* upgrade that server – in particular if it is a 5.0 before 5.0.15. You will continue to run into all sorts of problems if you don't!
LOAD LOCAL DATA INFILE {with parameters as you specified in the import dialogue).
So I am 99% sure that is is the server that breaks here!
But maybe it is documented like that somewhere.
(It is very difficult to convince anybody at MySQL AB that a documented behaviour may still be a bug!)
I can check later tonight. If I can confirm this and reproduce from command line client as well I will report to http://bugs.mysql.com
.. unles you prefer to do yourself (but report as an issue with LOAD DATA statement and not as an issue with SQLyog!). They will probably tell you in the first to use another 'terminated by' sequence than 'rn' .. but I think Excel won't let you configure that! So they will have to admit I think that the parser is too simple here! Unless it has been fixed in a later server version than yours already.
Could you zip and attach a small sample file to reproduce with?
Execute “SHOW WARNINGS” (will display warnings for last operation that affected a table – for more exact details refer to MySQL docs). For debugging insert “show warnings” statements in the SP code itself at appropriate places.
Better ideas out there?
Author
Posts
Viewing 15 posts - 3,106 through 3,120 (of 7,398 total)