- changed status to resolved
mapper include_properties parameter works differently in 0.6.3 and 0.6.4
Issue #1918
resolved
The attached patch fixes a regression in 0.6.4.
In 0.6.3 passing include_properties=[] to a mapper caused skipping of mapping table columns while in 0.6.4 - the opposite - all table columns will be automatically mapped.
When trying to add a property later a warning is generated: "SAWarning: Implicitly combining column users.status with column users.status under attribute 'status'. This usage will be prohibited in 0.7. Please configure one or more attributes for these same-named columns explicitly."
Comments (3)
-
repo owner -
repo owner -
repo owner - removed milestone
Removing milestone: 0.6.5 (automated comment)
- Log in to comment
looks good to me, thanks for the patch, 6409a06df190c8f6cc4a77e714aa989243af46f5