I'm using Hibernate Search with Annotations. I've created the index and have added the listeners so the index stays up to date when changes are made through the annotated entity. My problem is that we often have to run some update queries manually on our db because our application isn't fully developed for all functionality yet.

Is there a way, other than deleting the whole index and re-creating it, that we can keep the index up to date during non-hibernate updates??

Thanks so much for any help.

Hi,

do you have a way to identify the updated values? For example do you have a [i]lastModified[i] timestamp or something similar. If so you can use the batch indexing functionality, but you just retrieve the entities which have an updated timestamp.

BTW, are these queries native SQL queries? Bottom line is that you somehow need an entity. Be it for batch indexing or incremental updates.

--Hardy

Well these are native SQL queries. We have a MS SQL Server 2005 db. We are literally opening Management Studio and executing queries to update data. Is there any way for hibernate to listen to changes to db tables that have an entity associated with them to keep the index updated?

...from what I've read I can't really see a way other than deleting the entire index and recreating it.

I think what I could do... maybe give me your feedback on this.

We need to run queries directly on the database for various tasks.
What if I created a function in my hibernate class that excepts a sql query as a string.
I can then create a separate page that only has a textbox and a submit button. I can place whatever sql code I need to execute in the textbox, click submit, and have it call the hibernate function with the passed sql code. That way, if its done inside the hibernate entity, the listener will pick it up.

Thoughts?

Hi,

If you are talking about using Hibernate's native query support you are still having the same problem. Yes, you can trigger any native query from within Hibernate, but that does not mean that Hibernate automatically knows which entities are effected by the query.

--Hardy