Re: maybe off topic JDBC question

Try add that into postgresql.conf:

add_missing_from = 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.

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).
)

> -----Original Message-----
> From: tony [mailto:tony(at)tgds(dot)net]
> Sent: Tuesday, December 20, 2005 12:25 PM
> To: pgsql-admin(at)postgresql(dot)org
> Subject: [ADMIN] maybe off topic JDBC question
>
>
> 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:
>
> I have migrated the backend from 7.2.1 to 8.1.1
> Most of the JSPs work just fine several others don't
>
> §§§§§§§§§§§§§§§§§
>
> org.postgresql.util.PSQLException: ERREUR: Entrée manquante de la
> clause FROM pour la table «individu»
>
> (translation: missing entry in the FROM clause of table...)
>
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(
> QueryExecu
> torImpl.java:1512)
>
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryE
> xecutorImp
> l.java:1297)
>
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutor
> Impl.java:
> 188)
>
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJd
> bc2Stateme
> nt.java:430)
>
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(A
> bstractJdb
> c2Statement.java:346)
>
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(Abstr
> actJdbc2St
> atement.java:250)
>
> org.apache.jsp.contact.fiche_005findividu_005fintra_jsp._jspSe
> rvice(org.
> apache.jsp.contact.fiche_005findividu_005fintra_jsp:71)
>
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServlet
> Wrapper.ja
> va:322)
>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet
> .java:314)
>
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> §§§§§§§§§§§§§§§§§§
>
> OK so far so good, now the crunch - I have a newer version of
> 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...
>
> I have run the query from the JSP in pgaccess and it works just fine.
>
> Tomcat was also updated from 4 to 5.5 and I have the latest
> postgresql.jar for JDK1.5
>
> Any thoughts?
>
> Cheers
>
> Tony
> --
> 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
> VIA Epia-M
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>