Hi all, if you have some real use case that require to change a little some Pivot classes (even that could change a little its API) maybe a JIRA ticket for our 2.1 release could be useful.
My point of view is to enable users to extend Pivot where needed. And Greg likes real use cases before changing anything in Pivot ... so write them (and if possible put even a reference to this thread). Bye Il giorno 06/ago/2011 20:05, "Bill van Melle" <[email protected]> ha scritto: > I remember facing a similar question when I wanted to add an http > timeout to GetQuery. These classes could be much more usefully > extended if some of their important locals were marked protected > instead of private. (Not that it's an easy decision to know when to > do that when you're implementing the base class. Pivot seems to take > the conservative approach of marking everything private for which > Pivot does not itself have a subclass that wants access.) > > On Sat, Aug 6, 2011 at 6:49 AM, Thomas G. Schuessler <[email protected]> wrote: >> I cannot access the connection since it is local to Query's execute method. >> The only ways I can think of to fix this, are: >> 1. Copy the complete Query.execute, modify it in MyPostQuery, and not call >> the inherited method at all. >> 2. Create my own abstract Query class and subclass that.
