I know that I shouldn't be using version 1.6.3 with schema revision 143 but we're using pawtucket2 develop as our front-end and pawtucket2 requires it.
Still, this bug will happen when 1.7 lands.
With whatever version (1.6.3 or 1.7) and database schema 143, go to "Manage" -> "My sets" and, for a set, click "Batch" or "Edit", either action will trigger the error.
This error is caused because 143.sql adds a new column 'deleted' to ca_set_items and the query being built will complain that the column 'deleted' is ambiguous because it exists in both ca_set_items and ca_objects tables.
Using version 1.6.3 with schema revision 143.
The ca_sets model in 1.7 has corrected SQL.