Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id CF1306321EB
	for <pgsql-sql-postgresql.org@mail.postgresql.org>;
	Fri, 21 May 2010 04:35:29 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 20846-07 for
	<pgsql-sql-postgresql.org@mail.postgresql.org>;
	Fri, 21 May 2010 07:35:21 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from tmailer.gwdg.de (tmailer.gwdg.de [134.76.10.23])
	by mail.postgresql.org (Postfix) with ESMTP id F323B6321BA
	for <pgsql-sql@postgresql.org>; Fri, 21 May 2010 04:35:21 -0300 (ADT)
Received: from mailer-b1.gwdg.de ([134.76.10.30] helo=mailbox.gwdg.de)
	by mailer.gwdg.de with esmtp (Exim 4.69)
	(envelope-from <tlange@gwdg.de>) id 1OFMlM-00019v-Dm
	for pgsql-sql@postgresql.org; Fri, 21 May 2010 09:35:20 +0200
X-Xeceived: from 84.132.162.11 (SquirrelMail authenticated user tlange)
	by mailbox.gwdg.de with HTTP; Fri, 21 May 2010 09:35:20 +0200
Message-ID: <4c9adb73ac8c64f2e94c62e8d5d2f4d7.squirrel@mailbox.gwdg.de>
In-Reply-To: <AANLkTin2YCjEqBfu9n_wYwrGccZ0uFTzc8ZyxfmXXGz5@mail.gmail.com>
References: <ed7837818fc165ea7ffdc2efadb4ddc3.squirrel@mailbox.gwdg.de>
	<AANLkTin2YCjEqBfu9n_wYwrGccZ0uFTzc8ZyxfmXXGz5@mail.gmail.com>
Date: Fri, 21 May 2010 09:35:20 +0200
Subject: Re: sorry, now with subject... trigger & nextval(seq)
From: tlange@gwdg.de
To: pgsql-sql@postgresql.org
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: (clean) by exiscan+sophie
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.011 tagged_above=-5 required=5
	tests=BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201005/98
X-Sequence-Number: 34146

> On Thu, May 20, 2010 at 5:52 PM,  <tlange@gwdg.de> wrote:
>
>> I'm new to triggers in PostgreSQL. I have to create a trigger on insert
>> to
>> increment a sequence to overcome MS-Access' limitation in acknowledging
>> serial "datatype".
>
> Uh?  Access doesn't need to acknowledge the serial datatype.
> At-least in recent versions auto increment is recognized by MS-Access
> just fine (I'm guessing this is due to the Return clause which the
> ODBC driver automatically calls).
>
Thanks Richard. Ok, I hope our Access version is not too old (97 or 2000 I
think) because I could not insert. I'll try the most recent ODBC driver
and follow also Adrians suggestion.

Torsten