When schema specified, change to use connection.setSchema() rather than connection Properties

Using Properties with a properties.setProperty("schema", ..) is not supported
by Postgres. Changing to use connection.setSchema() looks like a more
robust approach.

Author: rbygrave

ebean-datasource/src/main/java/io/ebean/datasource/pool/ConnectionPool.java

@@ -41,6 +41,7 @@ final class ConnectionPool implements DataSourcePool {
   private final String driver;
   private final String url;
   private final String user;
+  private final String schema;
   private final String heartbeatsql;
   private final int heartbeatFreqSecs;
   private final int heartbeatTimeoutSeconds;
@@ -112,6 +113,7 @@ final class ConnectionPool implements DataSourcePool {
     this.applicationName = params.getApplicationName();
     this.clientInfo = params.getClientInfo();
     this.queue = new PooledConnectionQueue(this);
+    this.schema = params.getSchema();
     this.user = params.getUsername();
     if (user == null) {
       throw new DataSourceConfigurationException("DataSource user is not set? url is [" + url + "]");
@@ -123,10 +125,6 @@ final class ConnectionPool implements DataSourcePool {
     this.connectionProps = new Properties();
     this.connectionProps.setProperty("user", user);
     this.connectionProps.setProperty("password", pw);
-    final String schema = params.getSchema();
-    if (schema != null) {
-      this.connectionProps.setProperty("schema", schema);
-    }
 
     Map<String, String> customProperties = params.getCustomProperties();
     if (customProperties != null) {
@@ -430,6 +428,9 @@ private void initConnection(Connection conn) throws SQLException {
     if (readOnly) {
       conn.setReadOnly(true);
     }
+    if (schema != null) {
+      conn.setSchema(schema);
+    }
     if (applicationName != null) {
       try {
         conn.setClientInfo("ApplicationName", applicationName);