Guys, I haven't yet seen a tool that can do any reliable automation for the migration you're talking about - would be good if someone does know of any.
Its still a sore point for RAD development and argued that this is magnified for RAD compared to more traditional approaches that usually include heaps of scrutiny before a db is cut and taken live. In either case though its almost inevitable that change will eventually be needed so that whole argument is a bit pointless really. I'd think one reason for the poor tooling support in this space is that the delta (D) is often not just the 'data' itself but often can include changed semantics that no tool could hope to understand and act upon. On the mechanics of tracking the physical changes I'd agree with Patrick its just about retaining history of the DDL along with required migration scripts. -- View this message in context: http://old.nabble.com/Question-on-Iterative-builds-and-DDLs-tp27310244s17564p27334452.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
