Re: Bad locking with MS-Access

Hello, Andreas!

You mentioned: "Use serial or serial4 to create auto-values. Don't use
any bigint-types like bigserial. Access doesn't like 8-byte-ints.".
Could you please explain why you don't recommend bigserial for primary key ?
I use bigserial primary keys in Postgres tables, and din't realise problems
with MS Access front-end. What problems could I expect ?
Thanks,

Zlatko

----- Original Message -----
From: "Andreas" <maps(dot)on(at)gmx(dot)net>
To: "Ets ROLLAND" <ets(at)rolland-fr(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Sunday, July 24, 2005 11:01 PM
Subject: Re: [GENERAL] Bad locking with MS-Access

> Ets ROLLAND schrieb:
>
>> For all the data created BEFORE the transfert to PostgreSQL, all works
>> fine.
>> For the records created SINCE this transfert, it is impossible to modify
>> or delete these records !?
>> MS-Access say that "The record is acceded by an other user", even I am
>> the only user.
>
>
> As Richard wrote in his mail, do set row versioning in the ODBC setup.
> Have a primary key in every table and a timestamp.
> Be careful not to use to big data types in PG that aren't supportet by
> Access.
>
> Use timestamp(0) to get timestamps compatible to Access' DateTime
> values.
> Use serial or serial4 to create auto-values. Don't use any
> bigint-types like bigserial. Access doesn't like 8-byte-ints. Keep in mind
> that Access' autovalues are signed, so they'll roll over at about 2
> billion.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend