[teiid-issues] [JBoss JIRA] Commented: (TEIID-1732) Native PG Connector does not pass back errors to client

[Graeme Gillies (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624876#comment-12624876 ] 

Graeme Gillies commented on TEIID-1732:
---------------------------------------

Sure thing.

The following is the perl code I am running against a vdb we have
{code}
#!/usr/bin/env perl

use strict;
use warnings;

use DBI;
use DBD::Pg;

my $dbh = DBI->connect("dbi:Pg:dbname=BneDS;host=teiid-devel.eng.bne.redhat.com;port=35432", 'teiid', 'teiid', {AutoCommit => 0})
    || die "Could not connect to database: $DBI::errstr";

my $query = <<QUERY;
    select * from Bugzilla.bugs limit 2;
QUERY

print "$query";
my $sth = $dbh->prepare($query);
$sth->execute();

while ( my ( $bug_id, $login_name ) = $sth->fetchrow_array() ) {
    print "$bug_id,\"$login_name\"\n";
}

$sth->finish();
$dbh->disconnect();
{code}

Note that this problem isn't present if using an ODBC connection. My understanding is, as of teiid 7.5 port 35432 emulates a native postgres connection as well, so connecting to it from other languages as per a normal postgres database is possible

> Native PG Connector does not pass back errors to client
> -------------------------------------------------------
>
>                 Key: TEIID-1732
>                 URL: https://issues.jboss.org/browse/TEIID-1732
>             Project: Teiid
>          Issue Type: Bug
>    Affects Versions: 7.5
>         Environment: Red Hat Enterprise Linux Server release 5.7 (Tikanga)
> JBoss EAP 5.1.1
> java version "1.6.0_20"
> OpenJDK Runtime Environment (IcedTea6 1.9.8) (rhel-1.22.1.9.8.el5_6-x86_64)
> OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
>            Reporter: Graeme Gillies
>            Assignee: Steven Hawkins
>
> Hi,
> When we have people connecting to the native postgres emulation component of teiid (port 35432) using say, perl, or python, they can connect and query stuff fine, but if they give it a bad query (for exammple, the statement "selectx * from table.name") we see an error in the server side long saying the syntax is incorrect, but this error is never passed back to the client. The client just sits there waiting for a response that never comes.
> Can we please have any and all errors returned back to the client correctly?
> Thanks,
> Graeme

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira