{"push_id":1251645534,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"5044489e622143d6efdb69fbbc383748618b5fe4","before":"33e425bcbc8a6812b8bd51dec7c10e525ec9c8df","commits":[{"sha":"08a8c04c09f0bca6f0799deb411e99cb0283bc87","author":{"name":"Oliver Woolgar","email":"6c9ebcd0b0737ef9e913c481705a1b79c76b0a8b@assuredsoftware.com"},"message":"Added fix for SQL \"ambiguous column name\" that will occur when combining the length() function with a SQL query that has a join clause. To fix I have explicitly specified the table name when building express value","distinct":true,"url":"https://api.github.com/repos/project-imas/encrypted-core-data/commits/08a8c04c09f0bca6f0799deb411e99cb0283bc87"},{"sha":"1d583346ef23e21220154a0ae1cb7ffd1e7116b0","author":{"name":"Oliver Woolgar","email":"6c9ebcd0b0737ef9e913c481705a1b79c76b0a8b@assuredsoftware.com"},"message":"Fix bug in handling expressionDescriptionTypeValue. Current implementation assumes that the name property of the passed NSExpressionDescription would be an entity name. However I am not sure this will ever be the case. I have added protection against this by ensuring the root expression entity is passed as a parameter so it can be used as a fall back","distinct":true,"url":"https://api.github.com/repos/project-imas/encrypted-core-data/commits/1d583346ef23e21220154a0ae1cb7ffd1e7116b0"},{"sha":"5044489e622143d6efdb69fbbc383748618b5fe4","author":{"name":"Daniel Broad","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@dorada.org"},"message":"Merge pull request #250 from oliverwoolgar/master\n\nFixes for \"ambiguous column name\" SQL Error and handling NSExpressionDecriptions","distinct":true,"url":"https://api.github.com/repos/project-imas/encrypted-core-data/commits/5044489e622143d6efdb69fbbc383748618b5fe4"}]}
{"actor":{"display_login":"DanielBroad"}}