Search Postgresql Archives

Re: [HACKERS] Invalid unicode in COPY problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Madison Kelly <linux@xxxxxxxxxxx>
Subject: Re: [HACKERS] Invalid unicode in COPY problem
From: Oliver Jowett <oliver@xxxxxxxxxxxxx>
Date: Mon, 09 May 2005 15:36:40 +1200
Cc: John Hansen <john@xxxxxxxxxxxxxx>, Tatsuo Ishii <t-ishii@xxxxxxxxx>, pgsql-general@xxxxxxxxxxxxxx, pgsql-hackers@xxxxxxxxxxxxxx
In-reply-to: <427D944B.2070708@alteeve.com>
References: <5066E5A966339E42AA04BA10BA706AE50A930C@rodrick.geeknet.com.au> <427D944B.2070708@alteeve.com>
Sender: pgsql-general-owner@xxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.7.3 (X11/20040803)

Madison Kelly wrote:

Is there a way to store the name in raw binary?


Yes: bytea.

-O

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Re: [HACKERS] Invalid unicode in COPY problem
  - From: John Hansen
- Re: [HACKERS] Invalid unicode in COPY problem
  - From: Madison Kelly

Prev by Date: Re: Howto prevent write based on date
Next by Date: = or := ?
Previous by thread: Re: [HACKERS] Invalid unicode in COPY problem
Next by thread: Re: [HACKERS] Invalid unicode in COPY problem
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux