[storm] Objects not notified when DB chnages

[James Henstridge]

Please CC the list when you reply, otherwise no one else will see the responses.

On Thu, Aug 21, 2008 at 6:01 PM, Gabriel Rossetti
<gabriel.rossetti at arimaz.com> wrote:
>> Storm is designed to run using serialised transactions.  This means
>> that within the transaction the database effectively provides a
>> snapshot of the database state for Storm to work with.  When you
>> commit a transaction and start another, you will see changes made by
>> other database connections.  Storm will invalidate its caches on
>> transaction boundaries.
>>
>> So the answer to your question is to commit your transactions.
>
> Ok, thanks, since I do mostly reading operations, I guess I should do a
> commit before I do a "find()", every time? I already do commits when I do
> writing operations. Won't doing commits too often slow down the system?

Where you commit your transactions depends on the application.  As
well as being the points where your changes are made visible to other
connections, the transaction boundaries are also the points where
outside changes are made visible to you.

James.