On Mon, Dec 5, 2011 at 2:35 AM, Reinier Balt <[email protected]> wrote: >> >> In Tracks' case, updated_at is not a rails internal field used to keep > track of >> database content because it's specifically added as part of several > migrations >> in the Tracks codebase. >> > > Not true. > The field was added by a migration to support the rails version that > introduced auto-mgt of updated_at. Tracks roots are very old :-) > >> This sounds like it could be a bug in our API. Steve, could you file an > issue for >> this in our bug tracker on Assembla >> (https://www.assembla.com/spaces/tracks-tickets/tickets). I can't specify >> when this might get looked at or fixed, but we've had a couple of people >> working on the API recently and they might be able to pick this up and fix > it. > > I don't think this can be fixed easily, see explanation of Christian. > > Reinier >
Learn something new everyday. :) I assumed since it was part of a migration that it was added manually. Forgot that you'd have to add migrations for rails internal stuff too with Tracks being as old as it is. Thanks! -- Matt _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
