Chris Holmes wrote:
To make this work right we'd either need FeatureSources to have a
transaction field (that would be used just for the hints), or else
make setTransaction() in FeatureSource.
Either way I feel like using Transaction hints to do rendering stuff
is stretching the design a
David Blasby wrote:
Jody,
There's no setTransaction() method in the FeatureSource.
The only way I can see to set a property for a Query operation is to
convert the FeatureSource to a FeatureStore and then call
setTransaction() on it. I was a bit worried about this not working
because I
Either way I feel like using Transaction hints to do rendering stuff
is stretching the design a slight bit too far. Perhaps put hints in
Query itself?
Thats what I first suggested, but jody said the way to go was to put it
in Transaction.
But, then it affect all future Queries on that
