Custom Query (2152 matches)
Results (469 - 471 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1053 | fixed | Deletion in Model API | dread | dread |
Description |
Currently in the API if you DELETE a package/group/user (and you have the required permissions) then it purges the object, when it should probably just set the state to deleted. There is no way to delete objects at the moment - changes to 'state' are ignored in the API. Do we need an alternative way to purge objects in the API? |
|||
#1054 | fixed | Ordering of resources | kindly | dread |
Description |
Changing an old resource and creating a new resource on the end results in the old resource moving to the end in the ordering. This breaks tests:
You can make a ckan test break with this patch: diff -r e6643cf1324c ckan/tests/models/test_resource.py --- a/ckan/tests/models/test_resource.py Wed Mar 23 13:25:52 2011 +0000 +++ b/ckan/tests/models/test_resource.py Wed Mar 23 19:22:35 2011 +0000 @@ -297,6 +297,8 @@ 'url':self.urls[1], 'format':u'OTHER FORMAT', 'description':self.description, 'hash':self.hash, 'id':original_res_ids[2]}, + { #new + 'url':'new'}, ] pkg.update_resources(res_dicts) model.repo.commit_and_remove() There seems to be a problem with vdm creating a replacement Resource for the old resource - because it has a duplicate position it is put to the end by the SQLAlchemy ordering_list function. |
|||
#1055 | fixed | @search_related tests not running | dread | dread |
Description |
Tests marked decorated "@search_related" should only be run against postgresql, but in fact they don't get run at all. |