On Wednesday, February 6, 2013 at 11:56, 2jt6w5k7mt@sneakemail.com (Zach Seaman znseaman-at-gmail.com |pg-gts/Basic|) wrote: >This a similar question to this one ><http://www.postgresql.org/message-id/4dda42060512140509xe8b130as@mail.gmail.com>, >so I have encoded a database with LATIN-1 as suggested >but can't copy a CSV file into a table within the database. > I may have missed something here... why would anyone suggest LATIN-1 in modern times? UTF-8 will do all of LATIN-1 and everything else as well. Except for legacy support why would anyone use anything other than UTF-8? (Of course there are those where UTF-16 is a better choice for their dominant language use, e.g. chinese.) Suggest you use UTF-8 database encoding and if there are no problems importing the .csv stay with UTF-8. OTOH if there are still problems when using UTF-8, stay with UTF-8 while you work out what it is in the .csv file that's causing the problem. Regards Gavan
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера