MySQL Bugs: #27262: Return fully qualified column names with all queries

Bug #27262	Return fully qualified column names with all queries
Submitted:	19 Mar 2007 16:19	Modified:	29 Dec 2009 6:39
Reporter:	Stephen Mossbarger	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Information schema	Severity:	S4 (Feature request)
Version:	Any	OS:	Any (Any)
Assigned to:		CPU Architecture:	Any
Tags:	absolute name, column name, fully qualified

Description:
As a programmer, I would like to see unambiguous, fully qualified column names returned with any output in which column names appear in results from a query.

By fully qualified, I mean in the format `databaseName`.`tableName`.`columnName` with case sensitivity.

This would help me prevent data collisions resulting from ambiguity among column names that are the same, in cases where I have no control over column naming, and I am using multiple tables and/or MySQL databases.

It makes no sense that I can use fully qualified names in the query, but results can not be returned fully qualified as well.

How to repeat:
Not applicable

Suggested fix:
I suggest a non-default query option that can be specified as part of a query statement, and possibly also a global DBMS configuration setting that is either/or or both, to explicitly get fully qualified names in query results.

Many thanks for writing a feature request.

There are two reason against case sensitive identifiers:

1) SQL Standard says it should be case insensitive

2) We are not able to support this because Windows file system is not supporting it.