Neo4j默认隔离级别疑问：基础版默认是什么？是否仅Java扩展为READ_COMMITTED？

Let me break these down clearly based on my hands-on experience with Neo4j across different setups:

• Question 1: Is Neo4j's default isolation level always READ_COMMITTED, or only when using Java extensions?
  Neo4j's default transaction isolation level is consistently READ_COMMITTED across all standard usage scenarios—this isn't restricted to Java extensions. The Java-focused documentation you looked at drills into Java-specific implementation details, but the core transaction engine enforces READ_COMMITTED as the default no matter if you're using Java extensions, Cypher shell, REST APIs, or other language drivers.

• Question 2: What's the default isolation level for the basic Neo4j edition without any extensions?
  For the base (community) edition of Neo4j with no extensions enabled, the default isolation level is still READ_COMMITTED. This is a core setting built into Neo4j's transaction system. If you need stricter isolation (like SERIALIZABLE), you can explicitly define it when starting a transaction (either via Cypher syntax such as BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE or driver-specific APIs), but READ_COMMITTED is the out-of-the-box default for all standard deployments.

内容的提问来源于stack exchange，提问作者elena