Re: migration error

ok good that sound good that is what it matter :) El jue., 12 dic. 2019 a las 21:35, Leó Horváth () escribió: > hey, thanks i solved it the problem was very trivial, thank you for your > help anyway!! > > Leó Horváth ezt írta (időpont: 2019. dec. > 12., Cs, 20:13): > >> Still the same, it didnt

Re: migration error

hey, thanks i solved it the problem was very trivial, thank you for your help anyway!! Leó Horváth ezt írta (időpont: 2019. dec. 12., Cs, 20:13): > Still the same, it didnt help sadly :( > > > DANIEL URBANO DE LA RUA ezt írta (időpont: > 2019. dec. 12., Cs, 20:10): > >> if your are using sqlite

Re: migration error

what still the same, what you did. what you did not be more explicit El jue., 12 dic. 2019 a las 20:15, Leó Horváth () escribió: > Still the same, it didnt help sadly :( > > > DANIEL URBANO DE LA RUA ezt írta (időpont: > 2019. dec. 12., Cs, 20:10): > >> if your are using sqlite db and is empty d

Re: migration error

Still the same, it didnt help sadly :( DANIEL URBANO DE LA RUA ezt írta (időpont: 2019. dec. 12., Cs, 20:10): > if your are using sqlite db and is empty delete it and remake migrations > > El jue., 12 dic. 2019 a las 18:54, Leó Horváth () > escribió: > >> Hi guys! >> >> When I Try to make a mig

Re: migration error

if no https://docs.djangoproject.com/en/3.0/topics/migrations/#django.db.migrations.Migration.initial or https://simpleisbetterthancomplex.com/tutorial/2016/07/26/how-to-reset-migrations.html all this choices you have El jue., 12 dic. 2019 a las 20:10, DANIEL URBANO DE LA RUA (< dannybombas...@gm

Re: migration error

if your are using sqlite db and is empty delete it and remake migrations El jue., 12 dic. 2019 a las 18:54, Leó Horváth () escribió: > Hi guys! > > When I Try to make a migration my console says the following: > "ValueError: Related model 'database_manager.Name' cannot be resolved" > > however, "

Re: migration error "geo_db_type" when using postgres as second database for geodjango

The backport isn't trivial because of this removal that happened on 1.9 which would need to be accounted for on 1.8: https://github.com/django/django/commit/3b570dbcdb605cc6ee7e8796e1533fdd40c92362 If someone wants to do that work, we could probably accept a patch for 1.8. On Monday, September

Re: migration error "geo_db_type" when using postgres as second database for geodjango

On 9/14/15 7:10 PM, Wenyao Xue wrote: Thanks, I guess I have to wait for 1.9 to release then 在 2015年9月15日星期二 UTC+8上午12:21:58，Tim Graham写道： This is a bug that will be fixed in Django 1.9. https://github.com/django/django/commit/0cc059cd104cdb70340bd08e597d403d80dc42a6

Re: migration error "geo_db_type" when using postgres as second database for geodjango

Thanks, I guess I have to wait for 1.9 to release then 在 2015年9月15日星期二 UTC+8上午12:21:58，Tim Graham写道： > > This is a bug that will be fixed in Django 1.9. > > > https://github.com/django/django/commit/0cc059cd104cdb70340bd08e597d403d80dc42a6 > > On Monday, September 14, 2015 at 7:35:15 AM UTC-4, Wen

Re: migration error "geo_db_type" when using postgres as second database for geodjango

This is a bug that will be fixed in Django 1.9. https://github.com/django/django/commit/0cc059cd104cdb70340bd08e597d403d80dc42a6 On Monday, September 14, 2015 at 7:35:15 AM UTC-4, Wenyao Xue wrote: > > I upgraded my router using allow_migrate, but it didn't solve my problem > > 在 2015年9月14日星期一 UT

Re: migration error "geo_db_type" when using postgres as second database for geodjango

I upgraded my router using allow_migrate, but it didn't solve my problem 在 2015年9月14日星期一 UTC+8下午6:37:56，Jani Tiainen写道： > > I guess you need to write a bit more: > > https://docs.djangoproject.com/en/1.8/topics/db/multi-db/#allow_migrate > > And sync_db is deprecated... > > On 14.09.2015 13:07, We

Re: migration error "geo_db_type" when using postgres as second database for geodjango

I guess you need to write a bit more: https://docs.djangoproject.com/en/1.8/topics/db/multi-db/#allow_migrate And sync_db is deprecated... On 14.09.2015 13:07, Wenyao Xue wrote: Following is my router for world app. No router for other two apps, since default database is used Settings: DATAB

Re: migration error "geo_db_type" when using postgres as second database for geodjango

Following is my router for world app. No router for other two apps, since default database is used Settings: DATABASE_ROUTERS = ['world.routers.GisRouter'] router.py in world app: class GisRouter(object): """ A router to control all database operations on models in the auth applicati

Re: migration error "geo_db_type" when using postgres as second database for geodjango

On 14.09.2015 11:58, Wenyao Xue wrote: Hi, I use mysql as default database and postgres for geodjango related appliction. my settings: DATABASE_ROUTERS = ['world.routers.GisRouter', 'rest_shop.routers.ShopRouter', 'rest_client.routers.ClientRouter'] DA

Re: Migration error

On 10-6-2012 21:00, Raitucarp wrote: > 'ENGINE': 'django.db.backends.sqlite3' > > I have a model such this: > > class Ngobrol(models.Model): > title = models.CharField(max_length=200, blank = True) > message = models.TextField('Message') > linkp = models.URLField(max_leng

Re: Migration error

Hi again, can you verify that there are two migration scripts in your migrations folder? if yes, did you run manage.py migrate after the initial fake migration? if not, i speculate, that you ran south only after you already changed the models to include the aa column. South needs to know the i

Re: Migration error

Remember that I using sqlite3. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/_AylyCZQ0yEJ. To post to this group, send email to django-users@googlegroups

Re: Migration error

@henzk I still get the error, when access admin: DatabaseError at /admin/ngobrol/ngobrol/ no such column: ngobrol_ngobrol.aa -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.co

Re: Migration error

Hi Raitucarp, you can use the convert_to_south command to convert an existing app (with existing database tables) to south. In your case a manage.py migrate ngobrol 0001 --fake followed by a "manage.py migrate ngobrol" should fix your issue (given that you ran south initially, before changin