true, I don't support the idea to enforce this, but it would be nice
to provide the correct default, or maybe log a warning.
each bridge could have a
boolean recommendAnalyzersOn();
?
2010/5/26 Emmanuel Bernard :
> I have been thinking some more and it looks like its a more general problem
> an
I have been thinking some more and it looks like its a more general problem and
not as easy a solution as it seems.
If you think about it many bridges should not be analyzed (date, URL, class,
numbers, enum etc: most of the built-in ones actually).
That being said a smart person might want to c
Makes sense, maybe we could default to untokenized? Same idea should apply
to the soon-to-be-added NumericFields.
Il giorno 20/mag/2010 14:58, "Emmanuel Bernard" ha
scritto:
Does it ever make sense to use @DateBridge without
@Field(index=Index.UN_TOKENIZED) or NO_NORM
I got caught up with doing
