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

Fix for inconsistent use of getSQLDeclaration #815

Merged
merged 6 commits into from
Mar 13, 2015
Merged

Conversation

Wilt
Copy link
Contributor

@Wilt Wilt commented Mar 11, 2015

I found an inconsistency in naming of the getSQLDeclaration method
I changed in 5 files getSqlDeclaration -> getSQLDeclaration

Pull request is related to : doctrine/orm#1329

Fixed inconsistent use of getSqlDeclaration method name
Fixed inconsistent use of getSQLDeclaration method
Fixed inconsistent use of getSQLDeclaration method
Fixed inconsistent use of getSQLDeclaration method
Fixed inconsistent use of getSQLDeclaration method
@doctrinebot
Copy link

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DBAL-1169

We use Jira to track the state of pull requests and the versions they got
included in.

Fixed inconsistent use of getSQLDeclaration method
@Ocramius
Copy link
Member

@Wilt did this actually cause any issue or is it just for the sake of consistency?

@Wilt
Copy link
Contributor Author

Wilt commented Mar 13, 2015

No bugs or anything dangerous, just for consistency and searchability. I tried to understand where and how this method was used and while searching (case sensitive) I noticed this...
Just thought a pull request would be appropriate.

@Ocramius Ocramius self-assigned this Mar 13, 2015
@Ocramius
Copy link
Member

👍

Ocramius added a commit that referenced this pull request Mar 13, 2015
Fix for inconsistent use of getSQLDeclaration
@Ocramius Ocramius merged commit facca9f into doctrine:master Mar 13, 2015
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants