It sounds good not to use more than one core, for sure I do not want to over
complicate this.
Yes I meant tables.
It's pretty simple.
Both table courses and languages has it's own primary key courseseqno and
languagesseqno
Both also have a foreign key "userid" that references the users table wi
Ahh sorry,
Now I understand,
Ok seems like a good solution, I just know need to understand how to query
multiple cores now :)
-Ursprungligt meddelande-
Från: Dariusz Borowski [mailto:darius...@gmail.com]
Skickat: den 11 januari 2013 15:15
Till: solr-user@lucene.apache.org
Ämne: Re: confi
Hi Dariusz,
To me this example has one table "user" and I have many tables that connects
to one user and that is what I'm unsure how how to do.
/Niklas
-Ursprungligt meddelande-
Från: Dariusz Borowski [mailto:darius...@gmail.com]
Skickat: den 11 januari 2013 14:56
Till: solr-user@luce
Hmm noticed I wrote I have 3 columns: users, courses and languages
I ofcourse mean I have 3 tables: users, courses and languages
/Niklas
-Ursprungligt meddelande-
Från: Niklas Langvig [mailto:niklas.lang...@globesoft.com]
Skickat: den 11 januari 2013 14:19
Till: solr-user@lucene.apache.o
When thinkting some more,
Perhaps I could have coursename and such as multivalue?
Or should I have separate indeces for users, courses and languages?
I get the feeling both would work, but now sure which way is the best to go.
When a user is updating/removing/adding a course it would be nice to
