X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 9493F9DCA3D for ; Tue, 20 Dec 2005 06:20:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 42828-08 for ; Tue, 20 Dec 2005 06:20:21 -0400 (AST) X-Greylist: delayed 01:03:56.640546 by SQLgrey- Received: from backup.rambler.ru (backup.rambler.ru [81.19.66.56]) by postgresql.org (Postfix) with ESMTP id 23DC29DCA36 for ; Tue, 20 Dec 2005 06:20:12 -0400 (AST) Received: from office.rambler.stack.net ([81.19.65.34]) by backup.rambler.ru (8.12.10/8.12.10) with ESMTP id jBKAKDWT040462; Tue, 20 Dec 2005 13:20:13 +0300 (MSK) Received: by office.rambler.stack.net with Internet Mail Service (5.5.2657.72) id ; Tue, 20 Dec 2005 13:20:13 +0300 Message-ID: <291ABF6CBE162F45B006AFF7AB770B8806F8A7C2@office.rambler.stack.net> From: Boguk Maxim To: "'tony'" , pgsql-admin@postgresql.org Subject: Re: maybe off topic JDBC question Date: Tue, 20 Dec 2005 13:20:10 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200512/213 X-Sequence-Number: 19933 Try add that into postgresql.conf: add_missing_from =3D on More details look here: http://www.postgresql.org/docs/8.1/interactive/runtime-config-compatible= .htm l ( add_missing_from (boolean) When on, tables that are referenced by a query will be automatically = added to the FROM clause if not already present. This behavior does not = comply with the SQL standard and many people dislike it because it can mask mistakes (such as referencing a table where you should have referenced = its alias). The default is off. This variable can be enabled for = compatibility with releases of PostgreSQL prior to 8.1, where this behavior was = allowed by default.=20 Note that even when this variable is enabled, a warning message will be emitted for each implicit FROM entry referenced by a query. Users are encouraged to update their applications to not rely on this behavior, = by adding all tables referenced by a query to the query's FROM clause (or = its USING clause in the case of DELETE).=20 ) > -----Original Message----- > From: tony [mailto:tony@tgds.net] > Sent: Tuesday, December 20, 2005 12:25 PM > To: pgsql-admin@postgresql.org > Subject: [ADMIN] maybe off topic JDBC question >=20 >=20 > Ok this is probably a JDBC thing but as many admins seem to be = running > webapps and it is a version migration problem I shall ask here: >=20 > I have migrated the backend from 7.2.1 to 8.1.1 > Most of the JSPs work just fine several others don't >=20 > =A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7 >=20 > org.postgresql.util.PSQLException: ERREUR: Entr=C3=A9e manquante de = la =20 > clause FROM pour la table =C2=ABindividu=C2=BB >=20 > (translation: missing entry in the FROM clause of table...) > =20 > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse( > QueryExecu=20 > torImpl.java:1512) > =20 > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryE > xecutorImp=20 > l.java:1297) > =20 > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutor > Impl.java:=20 > 188) > =20 > org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJd > bc2Stateme=20 > nt.java:430) > =20 > org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(A > bstractJdb=20 > c2Statement.java:346) > =20 > org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(Abstr > actJdbc2St=20 > atement.java:250) > =20 > org.apache.jsp.contact.fiche_005findividu_005fintra_jsp._jspSe > rvice(org.=20 > apache.jsp.contact.fiche_005findividu_005fintra_jsp:71) > =20 > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > =20 > org.apache.jasper.servlet.JspServletWrapper.service(JspServlet > Wrapper.ja=20 > va:322) > =20 > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet > .java:314) > =20 > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) >=20 > =A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7=A7 >=20 > OK so far so good, now the crunch - I have a newer version of=20 > one of the > broken pages which uses the exact same JDBC connection code and it > works. The only modifications in the new page are use of style sheets > for layout instead of tables... >=20 > I have run the query from the JSP in pgaccess and it works just fine. >=20 > Tomcat was also updated from 4 to 5.5 and I have the latest > postgresql.jar for JDK1.5 >=20 > Any thoughts? >=20 > Cheers >=20 > Tony > --=20 > Tony Grant > www.tgds.net - vente d'ordinateurs mini-itx en ligne > www.tgds.net/epiaix1.html - A fedora Core 4 based live CD for=20 > VIA Epia-M >=20 >=20 > ---------------------------(end of=20 > broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster >=20