[ckan-dev] Deleting revisions & 'current' flag

[Ross Jones]

That's likely to be my fault, sorry for wasting your time on that, but thanks for finding it - might be good for us to have some internal consistency when something finds more than one active revision of an object.   I'll ask David next time we speak.

From what I recall there was a problem with using the logic layer because of the revisioning, hence the rather painful SQL.

Ross


On 18 Jul 2012, at 08:38, David Read wrote:

> No worries, it was just a DGU one.
> 
> Dave
> 
> On 18 July 2012 01:03, David Raznick <kindly at gmail.com> wrote:
>> On Tue, Jul 17, 2012 at 3:48 PM, David Read
>> <david.read at hackneyworkshop.com> wrote:
>>> In tracking down this problem it appears to be because of a ropey
>>> migration script that amended the member_revision table.
>>> 
>>> Lesson to learn: avoid using SQL when safer higher level functions
>>> exist for manipulating the model.
>>> 
>>> David
>> 
>> Hello,
>> 
>> Was that migration script part of core or was it one for dgu?  Just
>> worried if all our services are effected.
>> 
>> David
>> 
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
> 
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev