You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Java implementation, there is a JdbcDatabaseContainer abstract class(it should be an interface from the design view) and an R2dbcDatabaseContainer interface to unite the common properties when connecting Rdbms with JDBC or R2dbc driver.
In this PHP implementation, common properties such as databaseName, username, password, etc., are varied in different database containers.
These properties' naming looks a little tedious, we know the database type when creating the container, so why add database type as the prefix of these properties?
It is better to use some interface to unite these properties for Rdbms.
DatabaseName
Username
Password
TestQueryString
interface RdbmsContainer{
}
Or PdoDatabaseContainer and DoctrineDatabaseContainer to add driver-specific properties, as described in #23.
The text was updated successfully, but these errors were encountered:
In the Java implementation, there is a
JdbcDatabaseContainer
abstract class(it should be an interface from the design view) and anR2dbcDatabaseContainer
interface to unite the common properties when connecting Rdbms with JDBC or R2dbc driver.In this PHP implementation, common properties such as databaseName, username, password, etc., are varied in different database containers.
For example, MySQL:
and Postgres:
These properties' naming looks a little tedious, we know the database type when creating the container, so why add database type as the prefix of these properties?
It is better to use some interface to unite these properties for Rdbms.
interface RdbmsContainer{ }
Or
PdoDatabaseContainer
andDoctrineDatabaseContainer
to add driver-specific properties, as described in #23.The text was updated successfully, but these errors were encountered: