Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.5] Specify lower case column_name (fixes #20190) #21037

Merged
merged 1 commit into from
Sep 6, 2017

Conversation

laurenkt
Copy link
Contributor

@laurenkt laurenkt commented Sep 6, 2017

The MySqlProcessor assumes that the result from MySQL contains a lowercase column called column_name.

On my installation, if I run the query from compileColumnListing of MySqlGrammar

select * from information_schema.tables where table_schema = ? and table_name = ?

The result contains the column COLUMN_NAME in uppercase.

I don't really know where this is changed. In the driver? Maybe it makes sense to change the query in MySqlGrammar to ensure the correct case of the result:

select column_name as "column_name" from information_schema.tables where table_schema = ? and table_name = ?

In reference to: #20190

@themsaid themsaid changed the title Specify lower case column_name (fixes #20190) [5.5] Specify lower case column_name (fixes #20190) Sep 6, 2017
@taylorotwell taylorotwell merged commit 345f7c9 into laravel:5.5 Sep 6, 2017
@taylorotwell
Copy link
Member

Thanks

gonzahce added a commit to gonzahce/framework that referenced this pull request Sep 6, 2017
*      catch errors as well (laravel#21047)

* return  from Validator::setCustomMessages (laravel#21046)

*       show exception class in JSON (laravel#21043)

* [5.5] Removed listener listensFor (laravel#21039)

* remove listensFor

* remove listensFor

* Specify lower case `column_name` (fixes laravel#20190) (laravel#21037)

* [5.5] Add policies method to Gate (laravel#21036)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants