Hi,
sorry to bring this issue up again, but when starting the refactoring for
this issue (taking the approach
to make the bridge stateful) I noticed a problem. We thought that we could
introduce
FieldBridge#initalize(String fieldName, LuceneOptions options)
while removing the same parameters
What would option 2 gain? In particular what is the usefulness of the
Iterable?
If it's to get the list of fields to be used by FieldSelector that's probably
not correct as a given set operation might only affect a subset of the
potential fields.
On 19 sept. 2011, at 12:39, Hardy Ferentschik w
In case some missed the last IRC meeting.
master is where development occurs
stable is as far as I can guess a 4.0 branch where only changes targeted for
the 4.0 release should happen (ideally not at this stage besides doc).
___
hibernate-dev mailing li
Correction, I have misinterpreted things. The stable branch is used to prepare
releases.
Emmanuel
On 19 sept. 2011, at 15:28, Emmanuel Bernard wrote:
> In case some missed the last IRC meeting.
>
> master is where development occurs
> stable is as far as I can guess a 4.0 branch where only cha
On Sep 19, 2011, at 15:00, Emmanuel Bernard wrote:
> What would option 2 gain? In particular what is the usefulness of the
> Iterable?
> If it's to get the list of fields to be used by FieldSelector that's
> probably not correct as a given set operation might only affect a subset
> of the p
On 19 sept. 2011, at 23:14, Hardy Ferentschik wrote:
> On Sep 19, 2011, at 15:00, Emmanuel Bernard wrote:
>
>> What would option 2 gain? In particular what is the usefulness of the
>> Iterable?
>> If it's to get the list of fields to be used by FieldSelector that's
>> probably not correct a
