Using MySQL in commercial software: when should you review open-source obligations?

Using MySQL in commercial software does not require full disclosure of all proprietary code simply because it is labeled as 'commercial'. The review should separately examine the database server, client libraries or connectors and how they are integrated into the final deliverable. Internal deployment differs from external combination distribution; neither constitutes identical usage behaviors.

First confirm which licence you received

Oracle publicly provides MySQL's GPL and commercial licensing arrangements and advises users to review the specific license information in their downloaded packages. Commercial licenses should be judged based on the software covered by the contract, its subjects, purposes, and distribution scope; it cannot be assumed that a single procurement contract automatically resolves all third-party component issues. MySQL Official Licensing Information

When using community editions, save precise version information, download sources, LICENSEs, and related exception texts. Simply stating 'MySQL 8' or 'official driver' is often insufficient for completion of the review.

Distinguish three common scenarios

Only running within an organization. When no external copies of the program are delivered, the factual basis for a GPL analysis differs from that of external distribution. Whether a group company, outsourced team, or customer environment falls under the same internal scope requires verification based on actual legal relationships.

Independent application connects to a database service. It is important to check whether the application brings in GPL client code and the actual combination of the application with the database. The use of sockets or network protocols for communication are technical facts that cannot be used alone as a basis to exempt licensing obligations.

Database or connector included with product delivery. Further judgment is needed on whether it is an independent aggregation or a combined program, and the licensing and source code obligations of the distributed components must be fulfilled. It cannot be inferred that all proprietary code handling methods apply simply because there is MySQL in the installation package. GPLv2 Sections 2 and 3

A FOSS Exception is not a closed-source waiver

Oracle's current Universal FOSS Exception has clear objects and conditions, involving compliant free and open-source software (FOS) along with its corresponding source code. It cannot be used as a general authorization for any closed-source application to freely embed client libraries. Some older versions may still apply historical exceptions; these must be determined based on the actual distribution package. Exception Text and Historical Exception Explanation

What should the project review package contain?

Software Composition Analysis (SCA) can help identify these objects. Ultimately, whether adjustments need to be made to how proprietary code is published should be based on specific combination facts and licensing terms for judgment.

software composition analysis can help to take an inventory of these objects, and the eventual need to adjust the distribution of its own code should be judged on the basis of a specific combination of facts and enabling clauses.