It is stated in documentation that all read or write operations must
be called in a transactional context, see:

http://api.neo4j.org/current/org/neo4j/api/core/NeoService.html

The current state is that read operations may execute succesfully
without throwing an exception but it is not intended use.

On Mon, Dec 29, 2008 at 2:51 PM, Mwanji Ezana <mwa...@gmail.com> wrote:
> Hi Johan,
> Thanks for the clarification.
>
> On Mon, Dec 29, 2008 at 11:34 AM, Johan Svensson 
> <jo...@neotechnology.com>wrote:
>
>> Reading may however throw an exception depending on
>> what state the object being read is in.
>>
>
> Either way, please make the rule clear and consistent. I've found the
> transaction constraint fairly easy to work around by moving transaction
> management outside of the domain objects.
>
> Mwanji
_______________________________________________
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to