I've been given a pretty big MySql data dump file (943 Mb) to migrate to our 4D db. There are lots of tables, many of which I think are not needed for our purposes.
I want to break this file down into individual files for each table, to make it more manageable. So I created a method to parse the file and create a new file for each table. But ... The content all looks like gobbledygook when opened in 4D - eg: ,'xÃÃàThe character set is UTF-8. If I open it in BBEdit it looks fine (readable text). I can't even open it in Atom. Any ideas about this? If it's UTF-8 4D should be able to read it correctly, no? Pat -- ************************************************* CatBase - Top Dog in Data Publishing tel: +44 (0) 207 118 7889 w: http://www.catbase.com skype: pat.bensky ************************************************* ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************

