[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: POS Screen - Errors when posting an invoice
- Subject: Re: POS Screen - Errors when posting an invoice
- From: "Chris Travers" <..hidden..>
- Date: Sat, 31 May 2008 12:57:01 -0700
On Thu, May 29, 2008 at 6:35 PM, <..hidden..> wrote:
>
>
> Yes. Here are the errors I received. I cut out some misc. items from the
> log that were not relevant.
>
> ..hidden..:~/data> pg_dump -a tatylee > tatyleebackup.sql
> ..hidden..:~/data> psql -d ledgersmbtest -f tatyleebackup.sql
> SET
> SET
> SET
> SET
> psql:tatyleebackup.sql:15: ERROR: relation "acctrans_entry_id_seq" does
> not exist setval
> --------
>
>
> psql:tatyleebackup.sql:92: ERROR: relation "session_session_id_seq" does
> not exist setval
>
>
> psql:tatyleebackup.sql:120: ERROR: insert or update on table "acc_trans"
> violates foreign key constraint "acc_trans_chart_id_fkey"
> DETAIL: Key (chart_id)=(10014) is not present in table "chart".
> psql:tatyleebackup.sql:14190: ERROR: duplicate key violates unique
> constraint "chart_pkey"
> CONTEXT: COPY chart, line 1: "10001 1000 CURRENT ASSETS H A
> f
> "
> psql:tatyleebackup.sql:15151: ERROR: duplicate key violates unique
> constraint "defaults_pkey"
> CONTEXT: COPY defaults, line 2: "audittrail 1"
> psql:tatyleebackup.sql:15194: ERROR: duplicate key violates unique
> constraint "dpt_trans_pkey"
> CONTEXT: COPY dpt_trans, line 58: "10148 10081"
> psql:tatyleebackup.sql:24676: ERROR: relation "session" does not exist
> psql:tatyleebackup.sql:24677: invalid command \.
> psql:tatyleebackup.sql:25122: ERROR: duplicate key violates unique
> constraint "taxmodule_pkey"
> CONTEXT: COPY taxmodule, line 1: "1 Simple"
> psql:tatyleebackup.sql:25131: ERROR: duplicate key violates unique
> constraint "transactions_pkey"
> CONTEXT: COPY transactions, line 1: "10148 ap"
>
Hmm... Your backup/restore procedure is hosed-- stuff is restored in
the wrong order. Which version of PostgreSQL are you running?
Also some tables like defaults have differnet column names, so just
doing a data dump/restore may create problems (this is not the only
thing happening here though).
Best Wishes,
Chris Travers
Best Wishes,
Chris Travers