Closed pmjones closed 7 years ago
@pmjones
Thank you for pinging.
I am not sure what advantage do you see in moving to a separate class than passing the string?
@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...
@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?
@pmjones @pavarnos thank you.
The quoter is actually introduced in https://github.com/auraphp/Aura.Sql/pull/153 .
So I doubt about it.
Thanks. Temporary blindness: I cannot find the coverage report / percentage?
@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%.
@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.
@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.
@pmjones I am :+1: . So "go" .
good with me
Thanks folks. Back to #108 !
This PR creates separate quoter classes for each driver (notably mysql and sqlsrv).
@harikt @pavarnos Thoughts?