pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: COPY and custom datestyles. Or some other technique?
Date: Wed, 29 Mar 2023 20:50:57 -0500
Message-ID: <e38d14b4-7868-d42c-ff43-15f704e60e29@gmail.com> (raw)
In-Reply-To: <9aa715ce-9485-638f-6567-e642a50699c4@aklaver.com>
References: <c1b6aa5b-61ca-1ab6-6295-172fbc0f6c21@gmail.com>
	<9aa715ce-9485-638f-6567-e642a50699c4@aklaver.com>

On 3/29/23 18:31, Adrian Klaver wrote:
> On 3/29/23 16:24, Ron wrote:
>> Postgresql 13.10
>>
>> $ psql -h myhost.example.com -X dba \
>>          -c "\copy ${tbl} from '/var/lib/pgsql/Rdb/${tbl}.csv' WITH 
>> DELIMITER '|';"
>> ERROR:  date/time field value out of range: "2013061914122501"
>> CONTEXT:  COPY t_id_master, line 1, column update_timestamp: 
>> "2013061914122501"
>>
>> The timestamp format generated by a legacy dbms is YYYYMMDDHHmmSSCC (year 
>> to centisecond, with no delimiters).
>>
>> Is there any way to convince Postgresql to import these fields?
>
> One option:
>
> 1) Import into staging table as varchar field.

I had thought of that.

It would be really helpful to be able to reposition columns in tables.  That 
way, one could:
add the new TIMESTAMP column,
populate it using to_timestamp(),
drop the text column,
reposition the TIMESTAMP column to where it "should" be.

-- 
Born in Arizona, moved to Babylonia.





view thread (9+ messages)  latest in thread

Message-ID: <e38d14b4-7868-d42c-ff43-15f704e60e29@gmail.com>
Permalink:  ../e38d14b4-7868-d42c-ff43-15f704e60e29@gmail.com/
Also on:    postgresql.org/message-id/e38d14b4-7868-d42c-ff43-15f704e60e29@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: COPY and custom datestyles. Or some other technique?
  In-Reply-To: <e38d14b4-7868-d42c-ff43-15f704e60e29@gmail.com>
  References: <c1b6aa5b-61ca-1ab6-6295-172fbc0f6c21@gmail.com> <9aa715ce-9485-638f-6567-e642a50699c4@aklaver.com> <e38d14b4-7868-d42c-ff43-15f704e60e29@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox