: I am not sure I agree with that. i don't think i understand what part you don't agree with :)
: Document management systems are quite common these days, and people : are used to "checking out" a document, making changes, and checking : the entire document back in. : : In many ways Lucene can be viewed as a self-contained document mngt : system if you store every field. agreed. : If the user is savvy enough to 'rebuild' their documents from an : external source, then the fields do not need to be stored (just the : OID field for convenience). it's this rebuilding that people tend to dislike about the delete/re-add process that's currently neccessary to "update" a document in Lucene .. people don't wnat to have to be savvy enough to rebuild their documents from an external source, they want to throw a bunch of docs in, do some searches, pull a doc out, modify one field and throw it back in again. at least: that's how i would characterize most questions about "updating" docs. if the issue was just one of supporting an updateDoc(Document) method where the client is expected to "rebuild" the entire doc before calling the method, then we've already got that ... it's IndexWriter.updateDocument(Term,Document). -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
