Re: Django OperationalError

2015-03-15 Thread Petar Pilipovic
Solved it, the problem was in 3th party apps, I did as luis recommended, tanks for the help. all the best, Petar On Fri, Mar 13, 2015 at 4:45 AM, luis zarate wrote: > If you deleted your db and created again and the issue persist then maybe > the problem is in your apps. > > Try removing db, com

Re: Django OperationalError

2015-03-12 Thread luis zarate
If you deleted your db and created again and the issue persist then maybe the problem is in your apps. Try removing db, comment 3th party apps in settings and run migrate with only django core apps, put again 3th party apps and run migrate. El jueves, 12 de marzo de 2015, Collin Anderson escribi

Re: Django OperationalError

2015-03-12 Thread Collin Anderson
Hi, Do you have the correct file path set to your sqlite3 database? Does it have proper permissions? I found a similar issue here: https://www.pythonanywhere.com/forums/topic/1814/ Collin On Wednesday, March 11, 2015 at 2:04:45 AM UTC-4, Petar Pilipovic wrote: > > Hey Collin, > I have done wha

Re: Django OperationalError

2015-03-12 Thread Petar Pilipovic
Heh, lol, Ok tax Collin I will do that. I was thinking that i need to delete mine migration from the terminal, but I will try that, tnx 10.03.2015. 18.01, "Collin Anderson" је написао/ла: > Hi Petar, > > I'm actually not sure why you want to call sqlflush. If you're trying to > clear out the data

Re: Django OperationalError

2015-03-10 Thread Petar Pilipovic
Hey Collin, I have done what have you told me, but I still have that error, I even created data base on www.pythonanywhere.com, and amend mine setting.py file to use that db. I have manually deleted database and done syncdb, migrate etc. Here are the output for syncdb , and the

Re: Django OperationalError

2015-03-10 Thread Collin Anderson
Hi Petar, I'm actually not sure why you want to call sqlflush. If you're trying to clear out the database, you may need to delete the migrations table manually, but it just might be simpler to delete the either database and re-create it, rather than the individual tables. Collin On Friday, Ma

Re: Django OperationalError

2015-03-06 Thread Petar Pilipovic
Hello Collin, No the problem is, i have tried to drop mine migrations whit python manage sqlflush, then I have recreate the db whit python manage.py migrate. Here this is the all operation whit python manage sqlflush, syncdb, migrate . I have notice that there was no migration

Re: Django OperationalError

2015-03-06 Thread Collin Anderson
Hi, The problem is that django_session doesn't exist in your database. Either it was never created or it was created and then later deleted. Does running manage.py migrate re-create it? Collin On Monday, March 2, 2015 at 11:36:51 PM UTC-5, Petar Pilipovic wrote: > > Hello James, sorry for not

Re: Django OperationalError

2015-03-02 Thread Petar Pilipovic
Hello James, sorry for not uploading mine answer on this mater, I was busy whit something else this day, ok now back to mine Operational Error I have got. I tried to google some solution to this problem had no luck, and I did what have you told me. I heave done some python manage.py sqlflush a

Re: Django OperationalError

2015-02-27 Thread Petar Pilipovic
Hello James, will do but I am not at mine lap top atm, gona do it as soon as posible, tank you very much. On Saturday, February 28, 2015, James Schneider wrote: > Generally this happens when you don't apply the initial migration. Have you run 'python manage.py migrate' (assuming Django >= 1.7 sin

Re: Django OperationalError

2015-02-27 Thread James Schneider
s, collecting > static, making migrations to mine django application, I have experienced an > OperationError saying: > no such table: django_session > > You can find the rest of mine question here on stackoverflow > <http://stackoverflow.com/questions/28778126/django-operat

Django OperationalError

2015-02-27 Thread Petar Pilipovic
rest of mine question here on stackoverflow <http://stackoverflow.com/questions/28778126/django-operationalerror>, Can someone help me over come this error, tank you. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsub