Stephen Frost [EMAIL PROTECTED] writes:
When loading a rather large data set I started getting errors along
these lines:
psql:/home/sfrost/school/cs750/reality/dump-anonymized.postgres.sql:262:
WARNING: nonstandard use of escape in a string literal
LINE 1: ...XX
: pgsql-hackers@postgresql.org
Subject:Re: [HACKERS] PostgreSQL 8.2beta1 w/ VALUES
Stephen Frost [EMAIL PROTECTED] writes:
When loading a rather large data set I started getting errors along
these lines:
psql:/home/sfrost/school/cs750/reality/dump-anonymized.postgres.sql:262:
WARNING
Luke, et al,
* Luke Lonergan ([EMAIL PROTECTED]) wrote:
Except that one warning would not be accurate, because the
warning is per tuple. How is postgresql going to know that
the warning applies to the same set of data but just a
different tuple?
I didn't say it'd be easy. :)
If it's
Hi, Luke,
Luke Lonergan wrote:
If it's going to roll back the entire load after that one warning, it
should terminate there.
AFAIK, a warning is no reason for PostgreSQL to roll back anything.
That's the difference between a warning and an error.
HTH,
Markus
--
Markus Schaber | Logical
Luke Lonergan [EMAIL PROTECTED] writes:
If it's going to roll back the entire load after that one warning, it
should terminate there.
This was a warning, not an error.
regards, tom lane
---(end of broadcast)---
TIP 1: if
Greetings,
Was just playing with 8.2beta1 and importing some data from MySQL and
found something rather annoying. Not *100%* sure the best way to deal
with this, if there even is a way, but...
When loading a rather large data set I started getting errors along
these lines:
Anyhow, don't know if there's really a good solution but it'd be nice
to only get one warning, or one of a given type, or something, and to
Except that one warning would not be accurate, because the warning is
per tuple. How is postgresql going to know that the warning applies to
the
Josh,
Anyhow, don't know if there's really a good solution but
it'd be nice
to only get one warning, or one of a given type, or
something, and
to
Except that one warning would not be accurate, because the
warning is per tuple. How is postgresql going to know that
the warning
