| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | arnaud(dot)listes(at)codata(dot)eu |
| Cc: | pgsql-odbc(at)postgresql(dot)org, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: 'default nextval()' loses schema-qualification in dump ? |
| Date: | 2010-07-06 15:17:38 |
| Message-ID: | 28564.1278429458@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-odbc |
Arnaud Lesauvage <arnaud(dot)listes(at)codata(dot)eu> writes:
> As you have understood, I am not very savvy about postgresql's
> internals, but from what you say my guess is that the problem is int the
> psqlODBC is getting the default value of the sequence ?
I have no idea, because you haven't showed us what's happening, only
your oversimplified description of what's happening. We really need to
see the exact SQL used to define the table (copy that from your dump,
perhaps) as well as the exact SQL used in the misbehaving insert
commands.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2010-07-06 15:32:54 | Re: SQL Query Help Please ! |
| Previous Message | Sebastian Ritter | 2010-07-06 15:13:36 | Re: PostgreSQL trigger execution order |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Broersma | 2010-07-06 18:24:55 | Re: UPDATE statement value mutation |
| Previous Message | Arnaud Lesauvage | 2010-07-06 15:02:43 | Re: 'default nextval()' loses schema-qualification in dump ? |