| From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Ottavio Campana <ottavio(at)campana(dot)vi(dot)it>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Subject: | Re: problem with serial data type and access |
| Date: | 2008-05-16 14:18:43 |
| Message-ID: | 200805160718.43670.aklaver@comcast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday 15 May 2008 11:44 pm, Ottavio Campana wrote:
> Adrian Klaver ha scritto:
> >> The fact is that the serial data type is in pratice an integer, and when
> >> I also try to connect with pgadminIII I see an integer data type and not
> >> a serial. I think that since it sees an integer, it does not understand
> >> that it is a serial, and access does not recognize it as autoincrement.
> >>
> >> I'm stuck at this point...
> >
> > Did you mark this field as the primary key when you linked the table?
>
> yes I did
Just out of curiosity, create a test table using the WITH OIDS clause and a
serial data type column along with some test columns and try to INSERT a
record.
--
Adrian Klaver
aklaver(at)comcast(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Broersma | 2008-05-16 14:38:03 | Re: problem with serial data type and access |
| Previous Message | Andrew Sullivan | 2008-05-16 13:55:56 | Re: Postgresql MVCC, Read Committed Isolation Level and taking "snapshot" |