From: Jon A. <jon...@du...> - 2009-05-29 15:12:32
|
On May 28, 2009, at 5:10 PM, Mark Dominus wrote: > > Files can be copied from SDSC to NESCent with any of several methods, > including rsync. rsync will work fine for me if we need incremental updates, otherwise scp is faster. > Once at NESCent, someone (who?) will be responsible for executing > these > large SQL batch files to import the data into the Pg database. If > done > properly, the Unicode data will be transferred faithfully. Unless I hear otherwise from Hilmar, I'm assuming that person will be me. I'll be setting up the rsync transfers and the SQL imports. If the SQL inserts all contain UTF8 characters, then there should be no problem with the import into a UTF8 postgresql database. If there are non-UTF8 characters in the SQL file, they can be stripped out with iconv or converted with a shell program called "recode" > If this sounds like a bad idea, or if there are unanswered questions, > now is the time to speak up. I also agree that this is the best option to try first. -Jon ------------------------------------------------------- Jon Auman Systems Administrator National Evolutionary Synthesis Center Duke University http:www.nescent.org jon...@ne... ------------------------------------------------------ |