Re: BUG #7852: TeamPostgresql is giving error

The following bug has been logged on the website:

Bug reference: 7852
Logged by: Yogesh Khandelwal
Email address: yogesh(dot)khandelwal(at)emc(dot)com
PostgreSQL version: 9.0.8
Operating system: Linux
Description:

hi,

I've deployed TeamPostgreSQL on my server and trying to access my database
using that and getting the following error while trying to access the
schema/tables

There was a problem connecting to this database. The message from the
database server was:

java.lang.UnsupportedOperationException: Composite foreign keys are not
supported for foreign key 'qrtz_blob_listeners_trigger_name_fkey' in table
qrtz_blob_triggers at
dbexplorer.server.command.DatabaseStructureGetCommand.populateForeignKeyInformation(DatabaseStructureGetCommand.java:499)
at
dbexplorer.server.command.DatabaseStructureGetCommand.readSchemas(DatabaseStructureGetCommand.java:385)
at
dbexplorer.server.command.DatabaseStructureGetCommand.readSchemas(DatabaseStructureGetCommand.java:218)
at
dbexplorer.server.command.DatabaseStructureGetCommand.getDatabaseStructure(DatabaseStructureGetCommand.java:208)
at
dbexplorer.server.command.DatabaseStructureGetCommand.execute(DatabaseStructureGetCommand.java:83)
at dbexplorer.server.AJAXService.getDatabaseStructure(AJAXService.java:457)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
java.lang.reflect.Method.invoke(Unknown Source) at
com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:569) at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
at
com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at
dbexplorer.server.AJAXService.service(AJAXService.java:320) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:565) at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:521)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
at org.eclipse.jetty.server.Server.handle(Server.java:349) at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:449)
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:925)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:857) at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:76)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:609)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
at java.lang.Thread.run(Unknown Source)

On Feb 5, 2013 6:20 PM, <yogesh(dot)khandelwal(at)emc(dot)com> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 7852
> Logged by: Yogesh Khandelwal
> Email address: yogesh(dot)khandelwal(at)emc(dot)com
> PostgreSQL version: 9.0.8
> Operating system: Linux
> Description:
>
> hi,
>
> I've deployed TeamPostgreSQL on my server and trying to access my database
> using that and getting the following error while trying to access the
> schema/tables

Team PostgreSQL is a third party product, and you need to bring this up
with their support, since it's not an issue in postgresql.

/Magnus
>

On Tue, Feb 5, 2013 at 06:30:56PM +0100, Magnus Hagander wrote:
>
> On Feb 5, 2013 6:20 PM, <yogesh(dot)khandelwal(at)emc(dot)com> wrote:
> >
> > The following bug has been logged on the website:
> >
> > Bug reference: 7852
> > Logged by: Yogesh Khandelwal
> > Email address: yogesh(dot)khandelwal(at)emc(dot)com
> > PostgreSQL version: 9.0.8
> > Operating system: Linux
> > Description:
> >
> > hi,
> >
> > I've deployed TeamPostgreSQL on my server and trying to access my database
> > using that and getting the following error while trying to access the
> > schema/tables
>
> Team PostgreSQL is a third party product, and you need to bring this up with
> their support, since it's not an issue in postgresql.

FYI, TeamPostgreSQL has this to the bottom of their web pages to avoid
confusion:

TeamPostgreSQL is a project of Webworks (webworks.dk), and is not
affiliated with the PostgreSQL Project.
The PostgreSQL trademark is used with permission.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +