From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch>, <jorgens(at)coho(dot)net>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: @@IDENTITY (Was: Access - ODBC - serial problem) |
Date: | 2004-04-09 19:22:57 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B889FA2F@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Philippe Lang [mailto:philippe(dot)lang(at)attiksystem(dot)ch]
> Sent: 09 April 2004 13:33
> To: jorgens(at)coho(dot)net; pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Access - ODBC - serial problem...
>
> Is there a Postgresql ODBC driver guru that could give us an
> idea for a driver modification? I don't know the exact job of
> an ODBC driver, nor how it connects to Postgresql, so I
> cannot tell if it would be possible to modify the ODBC
> driver, and do something like a "SELECT @@IDENTITY" (which is
> a SQL Server 2000 call, correct).
>
> Since Microsoft is behind both Access and SQL Server, maybe
> nothing can be done in the driver itself, and I'll have to
> handle my insertions by hand, through pl/pgsql. But really,
> that's a serious limitation...
SELECT CURRENT_USER;
Though I suspect that is not what you want. Are you asking for the
driver to translate '@@IDENTITY' into 'CURRENT_USER'?
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-04-09 19:24:27 | Re: ODBC driver further developments? |
Previous Message | Dave Page | 2004-04-09 18:38:55 | Re: ODBC driver further developments? |