[JBoss JIRA] Created: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode
2:45 p.m.
MySQL connector assumes that database is running in ANSI mode rather than the default
mode
------------------------------------------------------------------------------------------
Key: TEIID-379
URL: https://jira.jboss.org/jira/browse/TEIID-379
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern
Reporter: Greg Haber
Assignee: Steven Hawkins
I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume that
it is connecting to a MySQL database running in "ANSI" SQL mode
For instance, we list in the capabilities class that MySQL supports || as a string
concatenation parameter, but it actually only supports it if the SQL mode
"PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set
when you set the "ANSI" meta-mode (see
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details).
This is a bad assumption as it is not the default setting for MySQL (the default sql-mode
setting is "", or no special modes). I took a look at some of the databases
used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that
they have sql-mode set to ANSI on the server side.
I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix
code in this regard, so Teiid has the same issue.
Two possible resolutions are:
-Rework the connector to remove any assumptions that sql-mode=ANSI
-set sql-mode to ANSI when establishing new connections to MySQL (this can be done by
sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a
connection).
Unfortunately there does not appear to be a way to set this mode via a JDBC connection
property - you need to send the "set" command after establishing the
connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:03 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode
[
https://jira.jboss.org/jira/browse/TEIID-379?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIID-379:
---------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
Fix Version/s: 6.0.0
Affects Version/s: 6.0.0
Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Complexity: Low
Priority: Optional (was: Major)
MySQL connector assumes that database is running in ANSI mode rather
than the default mode
------------------------------------------------------------------------------------------
Key: TEIID-379
URL: https://jira.jboss.org/jira/browse/TEIID-379
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern
Reporter: Greg Haber
Assignee: Steven Hawkins
Priority: Optional
Fix For: 6.0.0
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume
that it is connecting to a MySQL database running in "ANSI" SQL mode
For instance, we list in the capabilities class that MySQL supports || as a string
concatenation parameter, but it actually only supports it if the SQL mode
"PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set
when you set the "ANSI" meta-mode (see
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details).
This is a bad assumption as it is not the default setting for MySQL (the default sql-mode
setting is "", or no special modes). I took a look at some of the databases
used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that
they have sql-mode set to ANSI on the server side.
I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix
code in this regard, so Teiid has the same issue.
Two possible resolutions are:
-Rework the connector to remove any assumptions that sql-mode=ANSI
-set sql-mode to ANSI when establishing new connections to MySQL (this can be done by
sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a
connection).
Unfortunately there does not appear to be a way to set this mode via a JDBC connection
property - you need to send the "set" command after establishing the connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:03 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode
[
https://jira.jboss.org/jira/browse/TEIID-379?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-379:
--------------------------------------
This was covered through Defect Tracker #24994. The KI puts responsibility on the user to
update the ANSI mode (setting it through the documented url parameter didn't seem to
work). I'm fine with making the change to remove the KI and instead update the
session to force ANSI mode.
MySQL connector assumes that database is running in ANSI mode rather
than the default mode
------------------------------------------------------------------------------------------
Key: TEIID-379
URL: https://jira.jboss.org/jira/browse/TEIID-379
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern
Reporter: Greg Haber
Assignee: Steven Hawkins
Fix For: 6.0.0
I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume
that it is connecting to a MySQL database running in "ANSI" SQL mode
For instance, we list in the capabilities class that MySQL supports || as a string
concatenation parameter, but it actually only supports it if the SQL mode
"PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set
when you set the "ANSI" meta-mode (see
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details).
This is a bad assumption as it is not the default setting for MySQL (the default sql-mode
setting is "", or no special modes). I took a look at some of the databases
used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that
they have sql-mode set to ANSI on the server side.
I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix
code in this regard, so Teiid has the same issue.
Two possible resolutions are:
-Rework the connector to remove any assumptions that sql-mode=ANSI
-set sql-mode to ANSI when establishing new connections to MySQL (this can be done by
sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a
connection).
Unfortunately there does not appear to be a way to set this mode via a JDBC connection
property - you need to send the "set" command after establishing the connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:23 a.m.
New subject: [JBoss JIRA] Resolved: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode
[
https://jira.jboss.org/jira/browse/TEIID-379?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-379.
----------------------------------
Resolution: Done
Added session set to the MySQLTranslator afterConnectionCreation method. Still need to
remove the ki from the docs
MySQL connector assumes that database is running in ANSI mode rather
than the default mode
------------------------------------------------------------------------------------------
Key: TEIID-379
URL: https://jira.jboss.org/jira/browse/TEIID-379
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern
Reporter: Greg Haber
Assignee: Steven Hawkins
Priority: Optional
Fix For: 6.0.0
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume
that it is connecting to a MySQL database running in "ANSI" SQL mode
For instance, we list in the capabilities class that MySQL supports || as a string
concatenation parameter, but it actually only supports it if the SQL mode
"PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set
when you set the "ANSI" meta-mode (see
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details).
This is a bad assumption as it is not the default setting for MySQL (the default sql-mode
setting is "", or no special modes). I took a look at some of the databases
used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that
they have sql-mode set to ANSI on the server side.
I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix
code in this regard, so Teiid has the same issue.
Two possible resolutions are:
-Rework the connector to remove any assumptions that sql-mode=ANSI
-set sql-mode to ANSI when establishing new connections to MySQL (this can be done by
sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a
connection).
Unfortunately there does not appear to be a way to set this mode via a JDBC connection
property - you need to send the "set" command after establishing the connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] Reopened: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode
[
https://jira.jboss.org/jira/browse/TEIID-379?page=com.atlassian.jira.plug...
]
Steven Hawkins reopened TEIID-379:
----------------------------------
Set syntax was wrong
MySQL connector assumes that database is running in ANSI mode rather
than the default mode
------------------------------------------------------------------------------------------
Key: TEIID-379
URL: https://jira.jboss.org/jira/browse/TEIID-379
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern
Reporter: Greg Haber
Assignee: Steven Hawkins
Priority: Optional
Fix For: 6.0.0
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume
that it is connecting to a MySQL database running in "ANSI" SQL mode
For instance, we list in the capabilities class that MySQL supports || as a string
concatenation parameter, but it actually only supports it if the SQL mode
"PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set
when you set the "ANSI" meta-mode (see
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details).
This is a bad assumption as it is not the default setting for MySQL (the default sql-mode
setting is "", or no special modes). I took a look at some of the databases
used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that
they have sql-mode set to ANSI on the server side.
I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix
code in this regard, so Teiid has the same issue.
Two possible resolutions are:
-Rework the connector to remove any assumptions that sql-mode=ANSI
-set sql-mode to ANSI when establishing new connections to MySQL (this can be done by
sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a
connection).
Unfortunately there does not appear to be a way to set this mode via a JDBC connection
property - you need to send the "set" command after establishing the connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:17 a.m.
New subject: [JBoss JIRA] Updated: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode
[
https://jira.jboss.org/jira/browse/TEIID-379?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIID-379:
---------------------------------
Fix Version/s: 6.1.0
(was: 6.0.0)
Fixing based upon error reported by Davide Cerbo.
MySQL connector assumes that database is running in ANSI mode rather
than the default mode
------------------------------------------------------------------------------------------
Key: TEIID-379
URL: https://jira.jboss.org/jira/browse/TEIID-379
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern
Reporter: Greg Haber
Assignee: Steven Hawkins
Priority: Optional
Fix For: 6.1.0
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume
that it is connecting to a MySQL database running in "ANSI" SQL mode
For instance, we list in the capabilities class that MySQL supports || as a string
concatenation parameter, but it actually only supports it if the SQL mode
"PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set
when you set the "ANSI" meta-mode (see
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details).
This is a bad assumption as it is not the default setting for MySQL (the default sql-mode
setting is "", or no special modes). I took a look at some of the databases
used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that
they have sql-mode set to ANSI on the server side.
I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix
code in this regard, so Teiid has the same issue.
Two possible resolutions are:
-Rework the connector to remove any assumptions that sql-mode=ANSI
-set sql-mode to ANSI when establishing new connections to MySQL (this can be done by
sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a
connection).
Unfortunately there does not appear to be a way to set this mode via a JDBC connection
property - you need to send the "set" command after establishing the connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:03 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode
[
https://jira.jboss.org/jira/browse/TEIID-379?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-379.
----------------------------------
Resolution: Done
MySQL connector assumes that database is running in ANSI mode rather
than the default mode
------------------------------------------------------------------------------------------
Key: TEIID-379
URL: https://jira.jboss.org/jira/browse/TEIID-379
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern
Reporter: Greg Haber
Assignee: Steven Hawkins
Priority: Optional
Fix For: 6.1.0
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume
that it is connecting to a MySQL database running in "ANSI" SQL mode
For instance, we list in the capabilities class that MySQL supports || as a string
concatenation parameter, but it actually only supports it if the SQL mode
"PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set
when you set the "ANSI" meta-mode (see
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details).
This is a bad assumption as it is not the default setting for MySQL (the default sql-mode
setting is "", or no special modes). I took a look at some of the databases
used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that
they have sql-mode set to ANSI on the server side.
I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix
code in this regard, so Teiid has the same issue.
Two possible resolutions are:
-Rework the connector to remove any assumptions that sql-mode=ANSI
-set sql-mode to ANSI when establishing new connections to MySQL (this can be done by
sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a
connection).
Unfortunately there does not appear to be a way to set this mode via a JDBC connection
property - you need to send the "set" command after establishing the connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5495
days inactive
5551
days old
6 comments
2 participants
participants (2)
-
Greg Haber (JIRA) -
Steven Hawkins (JIRA)