Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/GoogleCloudPlatform/cloud-sql-jdbc-socket-factory/compare/v1.22.0...v1.23.0 below:

Comparing v1.22.0...v1.23.0 · GoogleCloudPlatform/cloud-sql-jdbc-socket-factory · GitHub

• Pricing

Failed to load repositories. Confirm that selected base ref is valid, then try again.

Loading

Failed to load repositories. Confirm that selected head ref is valid, then try again.

Loading

• 11 commits
• 44 files changed
• 3 contributors

1. Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

2. chore: Use domain name from JDBC URL for Postgres and Mysql, Part of #…

   …2043. (#2050)
   
   When connecting to a Cloud SQL database using a domain name like `db.example.com`, 
   you may now set the domain name in the JDBC URL. For example, you can use a URL like
   "jdbc:mysql://db.example.com/my-schema?socketFactory=socketFactory=com.google.cloud.sql.mysql.SocketFactory"
   
   The socket factory will detect "db.example.com" and look up the TXT record to resolve
   the instance name. 
   
   See #2043 for the whole feature definition.

   Configuration menu Browse the repository at this point in the history
3. Configuration menu Browse the repository at this point in the history
4. Configuration menu Browse the repository at this point in the history

5. refactor: Remove unnecessary pre-fetching from R2DBC. (#2107)

   When the java connector was refactored to use ConnectorConfig and ConnectionConfig value objects, it was no longer necessary to pre-fetch the connection configuration to ensure that enableIamAuth was set correctly. Also, this is inconsistent behavior compared to the JDBC socket factory.

   Configuration menu Browse the repository at this point in the history
6. Configuration menu Browse the repository at this point in the history

7. feat: Automatically configure connections using DNS. Part of #2043. (#…

   …2047)
   
   The dialer may be configured to use a DNS name to look up the instance
   name instead of configuring the connector with the instance name directly.
   
   Add a DNS TXT record for the Cloud SQL instance to a private DNS server
   or a private Google Cloud DNS Zone used by your application. For example:
   
   Record type: TXT
   Name: prod-db.mycompany.example.com – This is the domain name used by the application
   Value: my-project:region:my-instance – This is the instance connection name
   Configure the dialer with the cloudsqlconn.WithDNSResolver() option.
   Open a database connection using the DNS name:
   
   HOST: The domain name configured in your DNS TXT record.
   
   Base JDBC URL: jdbc:mysql://<HOST>/<DATABASE_NAME>
   
   SOCKET_FACTORY_CLASS: com.google.cloud.sql.mysql.SocketFactory
   
   The full JDBC URL for MySQL should look like this:
   
   String jdbcUrl = "jdbc:mysql://<HOST>/<DATABASE_NAME>?" 
       + "&socketFactory=com.google.cloud.sql.mysql.SocketFactory" 
       + "&user=<MYSQL_USER_NAME>" 
       + "&password=<MYSQL_USER_PASSWORD>";
   See also: the Cloud SQL Go Connector implementation
   
   Part of #2043

   Configuration menu Browse the repository at this point in the history

1. chore: Use domain name from R2DBC connections when configuring the co…

   …nnector. (#2103)
   
   Now, the connector will detect if the R2DBC HOST connection property contains a domain name or a
   Cloud SQL instance name. If HOST has a domain name, the connector will look up the domain name to
   determine the instance name.
   
   For example, if the R2DBC url is set to r2dbc:gcp:mssql://<DB_USER>:<DB_PASS>@db.example.com/db,
   the connector will lookup the TXT record for db.example.com. The record should contain a valid
   Cloud SQL instance name.
   
   Part of #2043

   Configuration menu Browse the repository at this point in the history
2. Configuration menu Browse the repository at this point in the history
3. Configuration menu Browse the repository at this point in the history

Loading

Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.

You can try running this command locally to see the comparison on your machine:
git diff v1.22.0...v1.23.0

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4