Re: [ADMIN] psql copy errors

2005-06-24 Thread Alvaro Herrera
On Fri, Jun 24, 2005 at 09:43:43AM -0500, Scott Marlowe wrote: > On Fri, 2005-06-24 at 00:52, ? wrote: > > David Bear: > > > > Yes. I agree with you. > > \copy is really too brittle. > > I wonder why \copy is not like oracle's sqlldr? > > I think sqlldr is m

Re: [ADMIN] psql copy errors

2005-06-24 Thread Scott Marlowe
On Fri, 2005-06-24 at 00:52, 李江华 wrote: > David Bear: > > Yes. I agree with you. > \copy is really too brittle. > I wonder why \copy is not like oracle's sqlldr? > I think sqlldr is more powerful. When using sqlldr,we can specify the > maximum error records we al

Re: [ADMIN] psql copy errors

2005-06-23 Thread 李江华
David Bear: Yes. I agree with you. \copy is really too brittle. I wonder why \copy is not like oracle's sqlldr? I think sqlldr is more powerful. When using sqlldr,we can specify the maximum error records we allow,and we can also specify the number we should co

Re: [ADMIN] psql copy errors

2005-06-23 Thread Vladimir Yevdokimov
On June 23, 2005 03:27 pm, David Bear wrote: > I'm finding the \copy is very brittle. It seems to stop for everyone > little reason. Is there a way to tell it to be more forgiving -- for > example, to ignore extra data fields that might exists on a line? > > Or, to have it just skip that offending

Re: [ADMIN] psql copy errors

2005-06-23 Thread Michael Fuhr
On Thu, Jun 23, 2005 at 12:27:44PM -0700, David Bear wrote: > > I'm finding the \copy is very brittle. It seems to stop for everyone > little reason. Is there a way to tell it to be more forgiving -- for > example, to ignore extra data fields that might exists on a line? > > Or, to have it just sk