Hi All, > > But...if it's just CSV files, can't you make them CSV tables? (if they're > partial data for an existing table, you can do a CSV file and then INSERT > INTO .... SELECT ... FROM ....)
CSV tables do not support NULLs. LOAD DATA INFILE does. And the CSV engine uses one particular set of delimiters - in practical cases, there are a lot of files that are 'delimited' in some way, just not exactly like the CSV engine does it (tab separated,semi-colon separated...) I like the idea pointed out earlier in the thread of having some engine (possible extended CSV) that supports some syntax for defining the delimiters and escaping (perhaps simply the LOAD DATA INFILE syntax will do). At some point a while ago I implemented a prototype (based on the SKELETON engine, but coded while looking at the CSV engine) that does this. This code is not of sufficient quality to consider, but the idea worked and I would love to see a feature like this. kind regards, Roland > > These days most of the importing I'm doing is the dump and load of InnoDB > tables to convert to innodb_file_per_table. Good to know about > that....before Jim's comment I hadn't known you could do multi-threaded load > data infile. (one of the curses of having used it for years is that I tend > not to keep up to date on things I don't use.....I was very surprised to > learn that mysqlbinlog had features to specify a start and stop position, > I'd been grepping and using head and tail!) > > -Sheeri > > > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > > -- Roland Bouman http://rpbouman.blogspot.com/ _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
