Re: database_check / Ticket #12

2005-09-02 Thread Martin Maney
On Fri, Sep 02, 2005 at 04:19:38PM -, Tim Keating wrote: > Arguably, making the canonical descriptor of your data structures the > database (which AFAIK is how Rails does it) has advantages over making > it the code and building the db from that. However, I don't foresee > django changing to t

Re: database_check / Ticket #12

2005-09-02 Thread Tim Keating
> Yes indeed. Like for example that it is in general NOT a single-step > process! Sometimes you *have* *to* make a partial change, futz with > things, then complete the change. The sane way to do that, IMO, is to > manipulate the database using a language designed for database > manipulation (e

Re: database_check / Ticket #12

2005-09-01 Thread Martin Maney
On Thu, Sep 01, 2005 at 10:59:12AM -0500, Brant Harris wrote: > field in a table needs to be changed. In MySQL it seems to be > relatively easy to figure it out with DESCRIBE table; harder in > Postgres; and I believe impossible in SQLite. So there are two ideas > from there: I think you've mis

database_check / Ticket #12

2005-09-01 Thread Brant Harris
Alright, so I'm trying to finish the database_check function in management.py to generate ALTER TABLE commands. Effectively I'm steamlining my own solution, but it was decided that the two-step process I made was too 'messy'. Anyhow I wanted some opinions: Here's the problem, it is impossible t