Correct. For the sake of the Lucene catalog you don't remove the record immediately but simply flag it as well. The only thing that you have to do with that is to add this flag in all your queries that are active in order not to include records that are flagged as "remove".
And you are done and sailing off for today :-) On Thu, Apr 22, 2010 at 6:02 PM, Jason King <[email protected]> wrote: > Now, how about getting records out of the catalog. When someone deletes > something, I just delete the record. There will be too much activity to hold > onto things. So if someone deletes a redirect, they get asked to confirm > they really want to, and when they click yes, I just delete the record. Now, > since that record is gone, it won't have an index bit, cause it is gone, but > there wouldn't be anything telling the catalog to remove it, and I can't > remove it remotely. > > Would it be best to create a table, just a simple table called something > like "deleteFromIndex" where it simply lists the primary key unique ID of > the record that was deleted, and as part of the catalog update script, a > loop is ran on this table deleting any records from the catalog that match > with the deletedtable. Then once it is confirmed that the catalog deleted > the record, remove that entry from the table as well. > > logical? -- See for yourself how easy it is to manage files today. Join the revolution! Razuna SaaS On-Demand - Hosted Digital Asset Management Solution http://www.razuna.com/ Razuna - Open Source Digital Asset Management http://www.razuna.org/ Follow us on Twitter http://twitter.com/razunahq -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
