I think I should also do the same way. Thanks Brain for pointing me to this
idea.
As per my db design I don't have any single key as PK, I'm thinking of
putting a new field called [say] coreId and make it PK with auto-increment
option[I'm using MySQL, btw], and this will solve the problem. I think
KK -
In my experience with multi-core, I've found that using the user record's
integer PK for each user core works well by still allowing the user to
update their email addresses / usernames over time.
cheers,
--bemansell
On May 17, 2009 10:39 PM, "KK" wrote:
Thank you Otis.
One silly questi
solr will not give any exceptions .atleast ,there is no code which
checks for that. choose names which are valid characters in url
On Mon, May 18, 2009 at 11:08 AM, KK wrote:
> Thank you Otis.
> One silly question, how would I know that a particular character is
> forbidden, I think Solr will giv
Thank you Otis.
One silly question, how would I know that a particular character is
forbidden, I think Solr will give me exceptions saying that some characters
not allowed, right?
Thank,
KK.
On Sun, May 17, 2009 at 3:12 AM, Otis Gospodnetic <
otis_gospodne...@yahoo.com> wrote:
>
> KK,
>
> That s
KK,
That should work just fine. Should any of the characters in email addresses
turn out to be forbidden, just replace them consistently. For example, if @
turns out to be the problem, you could simple replace it with _.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
-
