Skip to content

Removed the redundant usage of layer. #4375

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

Closed
wants to merge 4 commits into from
Closed

Removed the redundant usage of layer. #4375

wants to merge 4 commits into from

Conversation

h4ckninja
Copy link

Since DBAL is database abstraction layer, and is defined in the document as such, to me it reads funny to have it as database abstraction layer layer. It sounds nitpicky, I know, but I find it an easier read this way. Also, the possessive DBAL stuck out ("DBAL's layer") as the DBAL doesn't own a layer, it is the layer whereas Doctrine does own the layer and is properly defined in the header.

Since DBAL is database abstraction layer, and is defined in the document as such, to me it reads funny to have it as database abstraction layer layer. It sounds nitpicky, I know, but I find it an easier read this way. Also, the possessive DBAL stuck out ("DBAL's layer") as the DBAL doesn't own a layer, it is the layer.
@@ -1,12 +1,12 @@
.. index::
pair: Doctrine; DBAL

How to Use Doctrine's DBAL Layer
How to Use Doctrine's DBAL
================================
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please shorten the underline to match the length of the headline?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and it should be "Doctrine DBAL" now

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wouterj I can make the change, but I'm curious if you can explain your line of thinking a bit more so I can understand what you are looking for.

The reason I'm leaving Doctrine as possessive of the DBAL is that in the document, it is explained that the ORM component of Doctrine is a higher level of the DBAL. So Doctrine owns multiple components, making it possessive of the DBAL. That's my reasoning at least.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Of course :)

The database abstraction layer created by Doctrine is called "Doctrine DBAL", just like the object relation mapper is called "Doctrine ORM". While it's also the DBAL of the Doctrine Project, it's official name is "Doctrine DBAL". That's why I want to use "Doctrine DBAL" instead.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works for me. Changing.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wouterj Changed.

@xabbuh
Copy link
Member

xabbuh commented Oct 25, 2014

@micheal These are only little details, but they matter as well. 👍

@h4ckninja
Copy link
Author

@xabbuh Done. :)

@wouterj
Copy link
Member

wouterj commented Oct 26, 2014

Thanks!

How to Use Doctrine's DBAL Layer
================================
How to Use Doctrine DBAL
==========================
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to remove 2 == so that it has the same length as the title. Yep, this actually matters :).

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, I hope. I could have sworn I had things fixed properly already.

@weaverryan
Copy link
Member

Great, thanks so much @micheal!

weaverryan added a commit that referenced this pull request Oct 30, 2014
This PR was submitted for the 2.5 branch but it was merged into the 2.3 branch instead (closes #4375).

Discussion
----------

Removed the redundant usage of layer.

Since DBAL is database abstraction layer, and is defined in the document as such, to me it reads funny to have it as database abstraction layer layer. It sounds nitpicky, I know, but I find it an easier read this way. Also, the possessive DBAL stuck out ("DBAL's layer") as the DBAL doesn't own a layer, it is the layer whereas Doctrine does own the layer and is properly defined in the header.

Commits
-------

27339c7 One more again. I could have sworn I had them lined up.
84164fa Removed the possession from Doctrine.
693698e Shorten the = to match the length of the text.
5ea2902 Removed the redundant usage of layer.
@weaverryan weaverryan closed this Oct 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants