From: Ian B. <ia...@co...> - 2005-04-02 18:21:35
|
Ksenia Marasanova wrote: > On Apr 1, 2005 9:27 AM, Ian Bicking <ia...@co...> wrote: > >>I'm thinking of creating a SQLObject management command-line app. I'm >>curious what features people might want to see in such a thing. > > > Very cool and useful! Here are my 2 cents: > > "Record" sql queries that are generated by create / update / delete > commands. Useful for one-time data conversion, that can then be > performed on the developer machine and only SQL executed on the live > database. Hmm... you mean, keep a record of every SQL query while an application is running, to be rerun on a remote host? That seems slightly scary. That might be more reasonable when SQLObject has a better logging package (based on the logging standard module). > Not sure if this is part of db comparison / versioning system, but > anyway: generate "alter table ... add column" SQL in addition to > "create table" (handy for manually updating existing tables). For now I want to avoid automatic updating of databases -- there's often more rules than just dropping or adding columns (e.g., create a new column, update into that column from some previous column or combination of columns, then drop those other columns). I don't think it's too big a deal to custom-code those transformations. And you can do them through SQLObject itself, if you want to, since you'll be able to create Python scripts to do the updates. -- Ian Bicking / ia...@co... / http://blog.ianbicking.org |