This is not a solution in my case,

becasue the permissions of the groups, and the user groups can be changed, and it will make managing index to be a nightmare.

 anyway,

I appreciate the advice, maybe it will be useful for the other guys that asked this question.

  Sergiu

[EMAIL PROTECTED] wrote:

If you know ahead of time which documents are viewable by a certain user
group you could add a field, such as group, and then when you index the
document you put the names of the user groups that are allowed to view that
document.  Then your query tool can append, for example "AND
group:developers" to the user's query.  Then you will not have to merge
results.

-Will

-----Original Message-----
From: Sergiu Gordea [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 15, 2004 2:58 AM
To: Lucene Users List
Subject: Re: Searching against Database


Hi,

I have a simillar problem. I'm working on a web application in which the users have different permissions.
Not all information stored in the index is public for all users.


The documents in Index are identified by the same ID that the rows have in database tables.

I can get the IDs of the documents that can be accesible by the user, but if this are 1000, what will happen in Lucene?

Is this a valid solution? Can anyone provide a better idea?

Thanks,

Sergiu


lingaraju wrote:



Hello

Even i am searching the same code as all my web display information is
stored  in database.
Early response will be very much helpful

Thanks and regards
Raju

----- Original Message ----- From: "Hetan Shah" <[EMAIL PROTECTED]>
To: "Lucene Users List" <[EMAIL PROTECTED]>
Sent: Thursday, July 15, 2004 5:56 AM
Subject: Searching against Database







Hello All,

I have got all the answers from this fantastic mailing list. I have
another question ;)

What is the best way (Best Practices) to integrate Lucene with live
database, Oracle to be more specific. Any pointers are really very much
appreciated.

thanks guys.
-H


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to