As a project evolves, database schema changes: tables come and go, columns come and go, relations come and go.
In Sqlalchemy, there is a way to track the changes, and create a small module to apply changes to production as development produces fixed in time deltas. Is there an accepted practice with Wt for creating / managing small modules to update schema changes without dumping, deleting, creating, and reloading a database each time? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
