On Jul 27, 2007, at 4:18 PM, Paul Johnston wrote:
> 1) Build python table definitions from a live database (i.e. AutoCode) > 2) Tell you where a MetaData differs from a live database > 3) Automatically build migrate scripts for simple database changes > (e.g. > adding a column) > > Now, I think we're hitting the limits of having such tools in the > UsageRecipes on the Wiki. Mike - is this something you'd be > prepared to > have in SQLAlchemy, perhaps in a "scripts" subdirectory? Otherwise, I > wonder if we should pick up the migrate project again and add these > kinds of abilities. > I would favor having ALTER TABLE constructs available within SA's compiler objects. also the table.compare(someothertable) is fine as well provided its done in a nice, succinct way (i.e. a 'compare()' method on all SchemaItems called recursively...no hacky stuff). > One other thing while I remember, how about adding a function > all_table_names (to return list of table names in a live database) to > each database's dialect? This would get rid of database-dependent code > in tools like AutoCode. yeah i replied to your msg several days ago that all_table_names is definitely useful. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
