Pretty sure a primary key is a pre-requisite for an updatable result set.
On Wed, Mar 14, 2012 at 9:03 AM, <patrick(dot)balleux(at)gmail(dot)com> wrote:
> Hello all,
> I have a table in a database that does not have a primary key. In the process of migrating data from Oracle to Postgres, I am using ResultSets to populate the Postgres tables.
> Basically, all is working well except for tables that do not have a primary key. When I reach the "movetoinsertrow" instruction in my code, the jdbc driver raises an exception about the missing primary key.
> The workaround would be to add a temporary primary key to such table, but I want to avoid that. I did the same test with HSQLDB and it works. To me, it seems like a bug.
> I googled around for the solution, but found nothing.
> Any tips?
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-jdbc by date
|Next:||From: Andrew Hastie||Date: 2012-03-14 14:46:07|
|Subject: Re: MoveToInsertRow on a table without a primary key|
|Previous:||From: patrick.balleux||Date: 2012-03-14 13:03:36|
|Subject: MoveToInsertRow on a table without a primary key|