I don't have any best practices to offer. I have been using Lucene with MySQL for an
year though.
All I do is store a key of some sort in the index
new Field("id", getPK(), true, false, false)
and then relate that to the database in code.
For "Live Oracle" databases, you might consider different things.
As I hear, Oracle lets you use Java in PL (no experience here). So you might consider
to add some code into the triggers to add and delete documents from the index. But
modifying the index is not as quick as modifying a database in most cases. So you
might want to come up with some sort of a compromise on this.
Perhaps more experienced users in this list will have better insights.
Hope that helps.
On Thu, 15 Jul 2004 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
