Re: [HACKERS] [GENERAL] Invalid unicode in COPY problem
| not null default false >> file_restore_display | boolean | not null default false >> file_restore | boolean | not null default false >>Indexes: >> "file_info_2_display_idx" btree (file_type,
Re: [HACKERS] [GENERAL] Invalid unicode in COPY problem
ignore the file. Is there a way to store the name in raw binary? If so, would this not be safe because to postgresql it should no longer matter what data is or represents, right? Maybe there is a third option I am not yet concidering? Madison -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Madison
