Does it ever make sense to use @DateBridge without
@Field(index=Index.UN_TOKENIZED) or NO_NORM
I got caught up with doing
@DateBridge(resolution=DAY) @Field
public String getDate() { return date; }
and having unexpected issues.
If it never makes sense we could raise an exception when that hap
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