From: | Sandeep Khandelwal <sandeep_khandelwal27(at)yahoo(dot)com> |
---|---|
To: | sdavis2(at)mail(dot)nih(dot)gov |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Bulk Load and Extract from PostgreSQL |
Date: | 2006-10-17 12:28:45 |
Message-ID: | 20061017122845.64792.qmail@web33313.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Hi Sean.
I will try you option. Thanks a lot for the information.
Thanks,
Sandeep
----- Original Message ----
From: Sean Davis <sdavis2(at)mail(dot)nih(dot)gov>
To: Sandeep Khandelwal <sandeep_khandelwal27(at)yahoo(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org
Sent: Tuesday, October 17, 2006 5:53:14 PM
Subject: Re: [INTERFACES] Bulk Load and Extract from PostgreSQL
On Tuesday 17 October 2006 08:18, Sandeep Khandelwal wrote:
> Hi Sean.
>
> The reference that you mentioned is just for Inclusion in the SQL commands
> directly. But.........
>
> I am trying to load coma seperated data using COPY FROM STDIN command (TEXT
> mode) and using PQputCopydata API. COPY FROM STDIN command requires user to
> specify coma seperated text version of all the data.
>
> My question is: If I have binary data(bytea) then I have to convert this
> data into string (char *) form and pass this data to PostgreSQL using
> PQputCopydata API. And, I don't have any API in Libpq to convert binary
> data into string.
Sandeep,
I see the issue--sorry about the misunderstanding. I'm not sure what the
"correct" answer is, but you could simply do base64 client-side encoding and
decoding of your data.
Sean
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Figueiredo Jr. | 2006-10-17 13:33:36 | Npgsql 1.0 Released!! |
Previous Message | Sean Davis | 2006-10-17 12:23:14 | Re: Bulk Load and Extract from PostgreSQL |