I need to amend what I said before; apparently, the 8.1.1 dump is creating correct sequence values
(except in one instance), but it's changing the names to "match" the tables and columns they go
with. Which is nice, I suppose, except that I use an object-relational mapping API that requires
hard
Brian Dimeler wrote:
Doing it that way doesn't produce any errors, but it still produces
incorrect sequence names and values.
Are these sequences that you created by hand and then associated with a
column? Versus using serial/bigserial types?
Sincerely,
Joshua D. Drake
Doug McNaught wrote:
Brian Dimeler <[EMAIL PROTECTED]> writes:
> In the database dump however, this default is omitted (and consequently, when
> restoring, the new
> server creates an implicit sequence named 'bands_dbbandcode_seq' instead of
> the correct
> bands_dbcode_seq, and it is never set to the correct value
Doing it that way doesn't produce any errors, but it still produces incorrect
sequence names and values.
Doug McNaught wrote:
Brian Dimeler <[EMAIL PROTECTED]> writes:
I'm trying to transition a database from one server to another, the
old one running Postgres 7.4.1 and the new, 8.1.1. When
Brian Dimeler <[EMAIL PROTECTED]> writes:
> I'm trying to transition a database from one server to another, the
> old one running Postgres 7.4.1 and the new, 8.1.1. When I try to
> restore using a pg_dump plaintext sql file from a nightly backup via
> the usual
>
> psql thedb < backup.sql
The bes
I'm trying to transition a database from one server to another, the old one running Postgres 7.4.1
and the new, 8.1.1. When I try to restore using a pg_dump plaintext sql file from a nightly backup
via the usual
psql thedb < backup.sql
It works for the most part, but encounters several errors
