On Sun, 6 Mar 2011, Dimitri Fontaine wrote:
Did you try pgloader yet?
Nope.
I did determine the reasons and fixed them so all rows read into the
table.
Thanks for the suggestion,
Rich
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscrip
Rich Shepard writes:
> I'm sure many of you have solved this problem in the past and can offer
> solutions that will work for me. The context is a 73-column postgres table
> of data that was originally in an Access .mdb file. A colleague loaded the
> file into Access and wrote a .csv file for me
On 02/23/2011 09:23 AM, Rich Shepard wrote:
> On Wed, 23 Feb 2011, David Johnston wrote:
>
>> Why can you not just import the CSV as generated by Access?
>
> I don't want additional quotation marks on all text.
I haven't followed this thread too closely, so maybe I'm missing
something, but isn
On Wed, 23 Feb 2011, David Johnston wrote:
Why can you not just import the CSV as generated by Access?
I don't want additional quotation marks on all text.
Loading the 80 rows in OO.o Calc does let me see the problems and I'm
fixing them one-by-one. I didn't think of doing this.
Thanks,
On Wednesday, February 23, 2011 6:11:16 am Rich Shepard wrote:
> On Tue, 22 Feb 2011, David Johnston wrote:
> > The data and table structure provided do not seem to correlate.
>
> David,
>
>That's the problem. However, they should match since they came from the
> same .mdb file.
>
> > Regard
ns and the record
should then import.
Repeat for all other records.
David J.
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Rich Shepard
Sent: Wednesday, February 23, 2011 9:11 AM
To: pgsql-general@postgresql.org
Subj
On Tue, 22 Feb 2011, David Johnston wrote:
The data and table structure provided do not seem to correlate.
David,
That's the problem. However, they should match since they came from the
same .mdb file.
Regardless, if you changed the delimiter to "|" from "," it is possible that
you conver
tine and
directly import the CSV into Postgres.
David J.
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Rich Shepard
Sent: Tuesday, February 22, 2011 9:59 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Finding Er
On Tue, 22 Feb 2011, Adrian Klaver wrote:
We are going to need to see at least a sample of the actual data in
one.csv that is causing the problem. You have an off by two error as you
suggest, but that could actually have happened earlier in the row. For
instance the well_finish_date would insert
On Tuesday, February 22, 2011 5:10:34 pm Rich Shepard wrote:
>I'm sure many of you have solved this problem in the past and can offer
> solutions that will work for me. The context is a 73-column postgres table
> of data that was originally in an Access .mdb file. A colleague loaded the
> file
On 02/22/2011 07:25 PM, Andy Colson wrote:
On 02/22/2011 07:10 PM, Rich Shepard wrote:
I'm sure many of you have solved this problem in the past and can offer
solutions that will work for me. The context is a 73-column postgres table
of data that was originally in an Access .mdb file. A colleagu
On 02/22/2011 07:10 PM, Rich Shepard wrote:
I'm sure many of you have solved this problem in the past and can offer
solutions that will work for me. The context is a 73-column postgres table
of data that was originally in an Access .mdb file. A colleague loaded the
file into Access and wrote a .c
I'm sure many of you have solved this problem in the past and can offer
solutions that will work for me. The context is a 73-column postgres table
of data that was originally in an Access .mdb file. A colleague loaded the
file into Access and wrote a .csv file for me to use since we have nothing
13 matches
Mail list logo
