>>Maybe Migrations is just really buggy? I am using PostgreSQL as the
backend. I added a column with a default value and then did makemigrations
then migrate. It doesn't work. I get a very long error<<
h.. I hope not. I'm using Postgres too. Looks like I'll have to add
a new field to my
Maybe Migrations is just really buggy? I am using PostgreSQL as the backend. I
added a column with a default value and then did makemigrations then migrate.
It doesn't work. I get a very long error.
> On Sep 7, 2014, at 8:54 AM, Malik Rumi wrote:
>
> Django 1.7rc2
Migrations in 1.7 is the replacement for south.
> On Sep 2, 2014, at 1:44 PM, Norman Bird wrote:
>
> OK, I found out that in order to change the schema of the tables one has to
> install and run a migration tool. I used south. just install south and check
> out their
Django 1.7rc2 here. Same question, same hope for an answer. It may be that
not all possible changes to a model are intended to be picked up. For
example, I created all my models directly in 1.7rc2, and I have not changed
any fields. What I have done is changed / added some meta and methods.
Well, it just came less than a day ago, so Google is probably still
catching up :)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Ok, I have version 1.6.5. I will see about updating. HmmmI had googled and
this is the first im hearing of this. Got to love Django. :-)
On Tuesday, September 2, 2014 5:40:52 PM UTC-4, Collin Anderson wrote:
>
> The newest version of django, version 1.7, has migrations built in.
>
--
You
The newest version of django, version 1.7, has migrations built in.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
OK, I found out that in order to change the schema of the tables one has to
install and run a migration tool. I used south. just install south and
check out their website for basic use and you basically run a few commands
from the command line and it sees the changes you made and migrate the
Very, very good question. I am experiencing the same issues with Django
1.7rc2 and 1.7rc3.
Syncdb and sql statements are intended for Django < 1.7.
Would love to hear a solution!
Op vrijdag 22 augustus 2014 09:32:43 UTC+2 schreef termopro:
>
> Hi there,
>
> I am using Django 1.7 RC2.
> I have
how about: python manage.py sql myapp
I just changed my model and I had to runt that in order to build the
tables.
On Fri, Aug 22, 2014 at 11:49 AM, Norman Bird
wrote:
> I stand corrected. :-)
>
>
> On Fri, Aug 22, 2014 at 11:47 AM, Larry Martell
I stand corrected. :-)
On Fri, Aug 22, 2014 at 11:47 AM, Larry Martell
wrote:
> On Fri, Aug 22, 2014 at 9:55 AM, Norman Bird
> wrote:
> > I am new, just completed the tutorials, but from my understanding you run
> > "python manage.py syncdb"
On Fri, Aug 22, 2014 at 9:55 AM, Norman Bird wrote:
> I am new, just completed the tutorials, but from my understanding you run
> "python manage.py syncdb" and that rebuilds the tables etc.
No, syncdb only create tables that do not exist. It does not alter any
existing
I believe so. Wont hurt to try it and see what happens.
On Fri, Aug 22, 2014 at 11:03 AM, Néstor wrote:
> is that true if the table is already there?
>
>
> On Fri, Aug 22, 2014 at 6:55 AM, Norman Bird
> wrote:
>
>> I am new, just completed the
is that true if the table is already there?
On Fri, Aug 22, 2014 at 6:55 AM, Norman Bird
wrote:
> I am new, just completed the tutorials, but from my understanding you run
> "python manage.py syncdb" and that rebuilds the tables etc.
>
> On Friday, August 22, 2014
I am new, just completed the tutorials, but from my understanding you run
"python manage.py syncdb" and that rebuilds the tables etc.
On Friday, August 22, 2014 3:32:43 AM UTC-4, termopro wrote:
>
> Hi there,
>
> I am using Django 1.7 RC2.
> I have created models and have run all the
Hi there,
I am using Django 1.7 RC2.
I have created models and have run all the migrations so Django created
tables in database.
Now i decided to change database table names and have added Meta class to
models containing table name:
class SomeModel(models.Model):
...
class Meta:
16 matches
Mail list logo