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

3.x quoter #132

Merged
merged 5 commits into from
Mar 20, 2017
Merged

3.x quoter #132

merged 5 commits into from
Mar 20, 2017

Conversation

pmjones
Copy link
Member

@pmjones pmjones commented Mar 19, 2017

This PR creates separate quoter classes for each driver (notably mysql and sqlsrv).

@harikt @pavarnos Thoughts?

@harikt
Copy link
Member

harikt commented Mar 19, 2017

@pmjones

Thank you for pinging.

I am not sure what advantage do you see in moving to a separate class than passing the string?

@pavarnos
Copy link
Contributor

@harikt it removes db specific config from the generic QueryFactory class https://github.com/auraphp/Aura.SqlQuery/pull/132/files#diff-f4d2c86a7d03f40d9533ddaca828a28fL47 into the db specific driver directory, which is an improvement in clarity. It makes the quoter re-usable too (eg in Aura.Sql?).

@pmjones how is the test coverage? I can't seem to find it...

@pmjones
Copy link
Member Author

pmjones commented Mar 19, 2017

@harikt As @pavarnos notes, it's "better form" than before, but not in any way functionally critical.

@pavarnos Test is at https://github.com/auraphp/Aura.SqlQuery/pull/132/files#diff-c13b8f7f14b2d2fbc0552d98128d064f and coverage should be the same as before (i.e. 100%); the db-specific quoters only modify properties, not methods. Cf. https://scrutinizer-ci.com/g/auraphp/Aura.SqlQuery/?branch=3.x

Other thoughts?

@harikt
Copy link
Member

harikt commented Mar 20, 2017

@pmjones @pavarnos thank you.

The quoter is actually introduced in auraphp/Aura.Sql#153 .

So I doubt about it.

@pavarnos
Copy link
Contributor

pavarnos commented Mar 20, 2017 via email

@pmjones
Copy link
Member Author

pmjones commented Mar 20, 2017

@harikt So is that a "yes" or a "no" on this PR?

@pavarnos At the Scrutinizer link, on the right, under "Badges", it shows 100%.

@harikt
Copy link
Member

harikt commented Mar 20, 2017

@pmjones I was answering to @pavarnos

It makes the quoter re-usable too (eg in Aura.Sql?).

The quoter is actually introduced in auraphp/Aura.Sql#153 .

So I doubt about it.

Probably the Quoter in that case can be moved out. But that may break what we advertise, but less things being duplicated.

@pmjones
Copy link
Member Author

pmjones commented Mar 20, 2017

@harikt Ah right. Yes, the quoter in Sql is much more limited.

@harikt @pavarnos Just so that we can either merge or close this PR, and I back to the "actual plan" laid out in #108 , give me "go" or "no-go" and I'll work from there.

@harikt
Copy link
Member

harikt commented Mar 20, 2017

@pmjones I am 👍 . So "go" .

@pavarnos
Copy link
Contributor

good with me

@pmjones pmjones merged commit c0876e1 into 3.x Mar 20, 2017
@pmjones
Copy link
Member Author

pmjones commented Mar 20, 2017

Thanks folks. Back to #108 !

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.

3 participants