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
On our project we have 2 databases: MySql and HBase under Apache Phoenix library. The thing is, that these two databases need to use different databaseOperationLookup classes, because MySql uses standard "Insert", while Phoenix supports "Upsert" operation only (Upsert operation inserts rows into a database table if they do not already exist, or updates them if they do.).
It would be nice, if a user could configure different databaseOperationLookup classes for different db connections.
The text was updated successfully, but these errors were encountered:
Unfortunately, I haven't seen anything related to Phoenix in DBUnit. As this project relies on what DBUnit supports, it would be necessary to first submit an issue in the DBUnit project, this support could probably be done based on logic similar to what can be found in org.dbunit.ext.mssql.InsertIdentityOperation.
Once done, I would then be able to provide support for it here too.
On our project we have 2 databases: MySql and HBase under Apache Phoenix library. The thing is, that these two databases need to use different databaseOperationLookup classes, because MySql uses standard "Insert", while Phoenix supports "Upsert" operation only (Upsert operation inserts rows into a database table if they do not already exist, or updates them if they do.).
It would be nice, if a user could configure different databaseOperationLookup classes for different db connections.
The text was updated successfully, but these errors were encountered: