Allow reset for some query parts

[golgote]

What about:
public function orderBy(array $spec, $replace = false)
instead of : public function orderBy(array $spec)

This can be added to other clauses as well.
I personally need this because my query is built by different objects and each adds some clauses that might later need to be replaced by others.

[harikt]

How about send a PR and in case @pmjones finds the time he can merge if that is ok :-) .

[golgote]

OK I will do that ASAP. I was just checking if you were open to this change.
Thanks.

[yespire]

Which syntax is better:
1.
single reset() method handle all cases
query->reset() // -- all, paramter is mixed optional
query->reset('order_by') // -- single factor
query->reset(['order_by', 'cols'] // -- multi-factors

a set of specialized reset methods
query->reset() // -- all, no parameter
query->resetCols() // -- no parameter
query->resetOrderBy()

support both 1 + 2

[harikt]

PR #91 .

[pmjones]

There are now 2 PRs in for this issue: #91 and #94. I will pick one of them, or implement the functionality myself. Thanks for your patience!

[pmjones]

@golgote @yespire @gauthier @harikt --

I am considering a series of without*() methods that return a clone of the current query. E.g.:

$newQuery = $oldQuery->withoutWhere()->withoutCols()->withoutOrderBy();

That way the existing query continues to exist, and the new one can be independently modified.

Thoughts?

[pmjones]

No, on further consideration, we already have some reset*() methods that can be exposed without BC break. I'll expand on those instead. If the user wants a clone, they can clone.

[harikt]

@pmjones FYI in case if you missed the discussion on #91 (comment) .

[pmjones]

Addressed by #95 et al. Let me know if those do not server your purposes.