On 28 Jul 2009, at 17:54, Dan Kubb (dkubb) wrote:
> I've outlined some of my ideas for making auto-upgrade and auto- > migrate produce even tighter schemas here: > > http://wiki.github.com/datamapper/dm-core/roadmap > > So the idea is to use the smallest data type provided by the datastore > that still meets the constraints you defined for the property. I see what you're aiming for. That would mean you'd have to set a maximum validation to trick the database into using a large column though? I don't use auto-migrations in any production code though, so it doesn't affect me. What matters is being able to specify it in a manual migration (ideally without writing SQL by hand). > dm-migrations have stagnated a bit recently and IMHO don't offer too > much above what you get from other migration systems like AR's other > than a slightly different UI. I'd like to resolve this if we can, and > bring the API closer inline with DM's. Not only that, the auto- > migrate and "classical migrations" offered by dm-migrations don't > share much code, so there are subtle differences in schemas they > produce. On the roadmap is to unify the backend logic so that the > same code path is used to create/update schemas. This would be a massive help. I use auto_migrate only to produce bug reports, but it is frustrating not knowing if an issue might be rooted in our schema. (You can check by hand, but it'd increase confidence knowing the code was the same.) Cheers Ashley -- http://www.patchspace.co.uk/ http://www.linkedin.com/in/ashleymoran http://aviewfromafar.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
