On Feb 24, 9:54 am, ggavy wrote:
> Thanks. It's good to get a little second opinion. I'm sure I'll make
> the switch to migration tools eventually as things become a little
> more involved.
>
> Cheers
> gav
I think the only possible danger is that you might forget to toggle
an option like IS NU
Thanks. It's good to get a little second opinion. I'm sure I'll make
the switch to migration tools eventually as things become a little
more involved.
Cheers
gav
On Feb 24, 11:58 am, Mike Ramirez wrote:
> On Thursday, February 24, 2011 03:48:18 am ggavy wrote:
>
> > Hello everyone,
> > if
On Thursday, February 24, 2011 03:48:18 am ggavy wrote:
> Hello everyone,
> if I have a live app running off a postgres db (containing data)
> and I want to make reasonably simple schema (and possibly data
> content) changes, are there any dangers in just using pgadmin (e.g
> adding a column) a
On Thu, 2011-02-24 at 03:48 -0800, ggavy wrote:
> I'd keep my models.py up-to-date with any changes I make
> to the database (in case of future uses of the app). I haven't seen
> anything online warning me not to do it, but the separation worries me
> slightly
well, that is the way django does it
Hello everyone,
if I have a live app running off a postgres db (containing data)
and I want to make reasonably simple schema (and possibly data
content) changes, are there any dangers in just using pgadmin (e.g
adding a column) as opposed to using some type of migration software,
e.g. south. I
5 matches
Mail list logo
