Differences between running Derby in embedded mode and using the Network Server

This section describes the differences between running Derby in embedded mode and using the Network Server.

• Differences between the embedded client and the network client driver
  The following are known differences that exist between the Derby embedded driver and the network client driver.
• Updatable result sets
  In Derby, the functionality of updatable result sets in a server environment and in an embedded environment are similar, with the exception of the following differences.
• User authentication differences
  When you run Derby in embedded mode or when you use the Derby Network Server, you can enable or disable server-side user authentication. However, when you use the Network Server, the default security mechanism (CLEAR_TEXT_PASSWORD_SECURITY) requires that you supply both the user name and password.
• Differences in JDBC methods
  A few JDBC methods behave differently with the embedded driver from the way they behave with the client driver.
• Differences using the Connection.setReadOnly method
  In embedded mode, when the Connection.setReadOnly method has true as the parameter, the connection is marked as a read-only connection. When you use the Network Server, the Connection.setReadOnly(true) method is ignored, and the connection is not marked as a read-only connection.