Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id C2F92B5DBDA for ; Mon, 23 May 2011 22:05:05 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 55685-08 for ; Tue, 24 May 2011 01:04:58 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pw0-f46.google.com (mail-pw0-f46.google.com [209.85.160.46]) by mail.postgresql.org (Postfix) with ESMTP id 2CBF6B5D801 for ; Mon, 23 May 2011 22:04:58 -0300 (ADT) Received: by pwi15 with SMTP id 15so2823522pwi.19 for ; Mon, 23 May 2011 18:04:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:subject:date:user-agent:cc:references :in-reply-to:x-kmail-markup:mime-version:content-type :content-transfer-encoding:message-id; bh=HJUQ5s3JCLAaE66/AOWF4CeaVpOZccKZl4lKg0ILqws=; b=ha9Yck8P4re3DQ5GRrACZvDueWDw2l3xtfu/RqYGdyl067bvlWYzfXYFM5pXUpC0Cq 4IPST0FrI4XadsJE75s0T818ZRF8WdOmoGe0W85Eo54R05n/ZCj3kmX2AyWfeoNKHMY3 5N1Yn3aIfJ2GlXftrwjj8ZTiNJwUiIMWzJM84= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :x-kmail-markup:mime-version:content-type:content-transfer-encoding :message-id; b=keqOj/3CSX24EbuflWKfttYxHcjkwqxuj5gWhZMyY06q5IVMlh0RW9ub1L55dA28us Tqgd3P0lvPjES8Y69x+WhJ+I8/R/YUZpOef/NCBpVJCsD8wBezgJo2ZhKDWJmqiY/kJK 5U2nKrcfPWL+gms9jfVTajOU7RQiN7R125IFc= Received: by 10.68.28.137 with SMTP id b9mr2085200pbh.191.1306199097692; Mon, 23 May 2011 18:04:57 -0700 (PDT) Received: from tucker.localnet (c-24-17-164-54.hsd1.wa.comcast.net [24.17.164.54]) by mx.google.com with ESMTPS id t9sm4667017pbq.31.2011.05.23.18.04.54 (version=SSLv3 cipher=OTHER); Mon, 23 May 2011 18:04:55 -0700 (PDT) From: Adrian Klaver To: pgsql-sql@postgresql.org Subject: Re: problem with update data sets from front ends 8.4, Ubuntu 10.04 Date: Mon, 23 May 2011 18:04:52 -0700 User-Agent: KMail/1.13.5 (Linux/2.6.32-31-generic; KDE/4.4.5; i686; ; ) Cc: Dean le Roux References: <201105231853.47726.projserve@gmail.com> In-Reply-To: <201105231853.47726.projserve@gmail.com> X-KMail-Markup: true MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_1Qw2N91+9Z60YdB" Content-Transfer-Encoding: 7bit Message-Id: <201105231804.53450.adrian.klaver@gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.887 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RFC_ABUSE_POST=0.001, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201105/141 X-Sequence-Number: 35425 --Boundary-01=_1Qw2N91+9Z60YdB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Monday, May 23, 2011 9:53:47 am Dean le Roux wrote: > postgres 8.3 to 8.4 Open office base 3.2 Ubuntu 9.04 to 10.04 (new > install) Did the OO version change also? >=20 > I recently upgraded from Ubuntu 9.04 to Ubuntu 10.04. Security and other > updates have been effected. I used webmin to restore the databases. >=20 > Since migrating to Linux around 2006 we were successful in converting our > mdb file to postgresql - only one glitch was a difference in -1 as YES. We > successfully used the systems with open office as a front end for the last > few years. Until now - after the upgrade I can view data but not update > data. Usually, in Base, that indicates that it can not find a primary key. =46YI: The below is redundant: CONSTRAINT "FINANCEDETAILS_pkey" PRIMARY KEY ("FINDETID"), CONSTRAINT "FINANCEDETAILS_FINDETID_key" UNIQUE ("FINDETID") =46rom the docs: http://www.postgresql.org/docs/8.4/interactive/sql-createtable.html "Technically, PRIMARY KEY is merely a combination of UNIQUE and NOT NULL, b= ut=20 identifying a set of columns as primary key also provides metadata about th= e=20 design of the schema, as a primary key implies that other tables can rely o= n=20 this set of columns as a unique identifier for rows. " >=20 > Experience with sql is very limited as I have always used sql query > builders over the years. The system has worked well with multiple tables, > and in the past there was no problems with sending sql statements to > postgresql. >=20 > My problem in OOO 3.2 base (other front ends also) is that there is > continually a problem with not allowing queries to update data back to > postgresql. What are you using to connect to the database JDBC, ODBC, other? >=20 > I believe something has changed perhaps in sql from 8.3 to 8.4, or I have > missed something with restoring the files. Did you do a full restore or selective? >=20 >=20 > Any assistance offered will be appreciated. =2D-=20 Adrian Klaver adrian.klaver@gmail.com --Boundary-01=_1Qw2N91+9Z60YdB Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit

On Monday, May 23, 2011 9:53:47 am Dean le Roux wrote:

> postgres 8.3 to 8.4 Open office base 3.2 Ubuntu 9.04 to 10.04 (new

> install)

Did the OO version change also?

>

> I recently upgraded from Ubuntu 9.04 to Ubuntu 10.04. Security and other

> updates have been effected. I used webmin to restore the databases.

>

> Since migrating to Linux around 2006 we were successful in converting our

> mdb file to postgresql - only one glitch was a difference in -1 as YES. We

> successfully used the systems with open office as a front end for the last

> few years. Until now - after the upgrade I can view data but not update

> data.

Usually, in Base, that indicates that it can not find a primary key.

FYI:

The below is redundant:

CONSTRAINT "FINANCEDETAILS_pkey" PRIMARY KEY ("FINDETID"),

CONSTRAINT "FINANCEDETAILS_FINDETID_key" UNIQUE ("FINDETID")

From the docs:

http://www.postgresql.org/docs/8.4/interactive/sql-createtable.html

"Technically, PRIMARY KEY is merely a combination of UNIQUE and NOT NULL, but identifying a set of columns as primary key also provides metadata about the design of the schema, as a primary key implies that other tables can rely on this set of columns as a unique identifier for rows. "

>

> Experience with sql is very limited as I have always used sql query

> builders over the years. The system has worked well with multiple tables,

> and in the past there was no problems with sending sql statements to

> postgresql.

>

> My problem in OOO 3.2 base (other front ends also) is that there is

> continually a problem with not allowing queries to update data back to

> postgresql.

What are you using to connect to the database JDBC, ODBC, other?

>

> I believe something has changed perhaps in sql from 8.3 to 8.4, or I have

> missed something with restoring the files.

Did you do a full restore or selective?

>

>

> Any assistance offered will be appreciated.

--

Adrian Klaver

adrian.klaver@gmail.com

--Boundary-01=_1Qw2N91+9Z60YdB--