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
Wrong SQL query is generated when parent table having more than one primary key is referenced through foreign key in the child table
DBFlow Version: 4.2.4
Bug or Feature Request:
Fix the logic for creating SQL query when Parent table with more than 1 primary key is referenced through foreignKey in the child table
Description:
When a child table reference a parent table (having more than one primaryKey) through Foreign Key, the SQL query generated for the child table is wrong
Here is the example of the query generated for UPDATE operation.
@OverRide public final String getUpdateStatementQuery() { return "UPDATE ContactPhoneMapping SET contact_primaryId=?,contact_secondaryId=?,phoneNo=?,type=? WHERE contact_primaryId=?,contact_secondaryId=? AND phoneNo=?"; }
Notice that "AND" is missing in the where condition for "contact_primaryId" and "contact_secondaryId"
The text was updated successfully, but these errors were encountered:
Wrong SQL query is generated when parent table having more than one primary key is referenced through foreign key in the child table
DBFlow Version: 4.2.4
Bug or Feature Request:
Fix the logic for creating SQL query when Parent table with more than 1 primary key is referenced through foreignKey in the child table
Description:
When a child table reference a parent table (having more than one primaryKey) through Foreign Key, the SQL query generated for the child table is wrong
Here is the example of the query generated for UPDATE operation.
@OverRide public final String getUpdateStatementQuery() { return "UPDATE
ContactPhoneMapping
SETcontact_primaryId
=?,contact_secondaryId
=?,phoneNo
=?,type
=? WHEREcontact_primaryId
=?,contact_secondaryId
=? ANDphoneNo
=?"; }Notice that "AND" is missing in the where condition for "contact_primaryId" and "contact_secondaryId"
The text was updated successfully, but these errors were encountered: