Re: modeling multiple values on 1:n connection

On 23 June 2013 14:07, Mysurf Mail wrote: > Thanks for your comment. > What I need is to model it so that i can connect between the featureName > and the feature description of the. > Currently if item has 3 features I get two list - each three elements long. > But then I need to correlate them. [

Re: modeling multiple values on 1:n connection

en them), maybe in conjunction with a copyField of the raw, uncoordinated multvalued fields for easy query access. -- Jack Krupansky -Original Message- From: Mysurf Mail Sent: Sunday, June 23, 2013 4:37 AM To: solr-user@lucene.apache.org Subject: Re: modeling multiple values on 1:n conne

Re: modeling multiple values on 1:n connection

Thanks for your comment. What I need is to model it so that i can connect between the featureName and the feature description of the. Currently if item has 3 features I get two list - each three elements long. But then I need to correlate them. On Sun, Jun 23, 2013 at 9:25 AM, Gora Mohanty wrot

Re: modeling multiple values on 1:n connection

On 23 June 2013 01:31, Mysurf Mail wrote: > I try to model my db using > thisexample > from solr wiki. > > I have a table called item and a table called features with > id,featureName,description > > here is the updated xml (added

modeling multiple values on 1:n connection

I try to model my db using thisexample from solr wiki. I have a table called item and a table called features with id,featureName,description here is the updated xml (added featureName)