[storm] questions around "could not serialize access due to concurrent update"

[Martin DeMello]

>
> It is expected behaviour.  Each transaction works under the lie that
> it is the only one accessing the database (so can assume no one else
> is fiddling with the tables).  When the database realises that two
> transactions are relying on the same data it will kill one of them
> with a TransactionRollbackError.

Thanks!

martin