]
Steven Hawkins resolved TEIID-1732.
-----------------------------------
Fix Version/s: 7.4.1
7.6
Resolution: Done
The issue is with simple query error handling. It also matters that the sql started with
a malformed keyword. Perl Pg logic will issue an extended query if the sql starts with
"select", but a simple query for "selectx" and other non-recognized
sql. In the simple scenario we were not issuing a ready when an error was encountered.
Also added a minor fix that prevents errors from whitespace at the end of a single
delimited simple query.
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
Fix For: 7.4.1, 7.6
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: