Re: syncdb command can execute

Hi, Note that syncdb was deprecated in favor of migrations. Also if you have followed the official Django tutorial, second part of it goes through creating models and reflecting your models to database. https://docs.djangoproject.com/en/1.10/intro/tutorial02/ On 19.12.2016 12:56, Navneel Pan

Re: syncdb command can execute

Would you provide a little more information? What errors are you getting? On Mon, Dec 19, 2016 at 11:56 AM, Navneel Pandey wrote: > hi i am new to django as i want to create a table but unable to do so I am > writing the command python manage.py syncdb > > -- > You received this message because

Re: syncdb problem with mongodb engine

Hi, I was able to fix the problem by applying the patch here: https://bitbucket.org/andrewgodwin/south/pull-requests/86/fixing-the-keyerror-default-when-managerpy/diff Thanks, Lianghong On Monday, October 19, 2015 at 12:44:33 PM UTC-4, James Schneider wrote: > > The version of Django you are r

Re: syncdb problem with mongodb engine

The version of Django you are running has not been supported for quite a while, you should update your Django installation to 1.7 or 1.8. There may be a compatibility issue if you have a new version of the plugin but an old Django installation. You should also look to see if there is a support tic

Re: syncdb error with Mysql database on Windows 7

install PyMySQL, after create a user e a databases in mysql terminal; e.g:1º)create user 'root'@'localhost' identified by 'fish1777'; 2º) create database Mydb; 3º) grant all privileges on Mydb.* to 'root'@'localhost' identified by 'fish1777'; use syncdb. 2015-01-25 6:04 GMT-02:00 olek.russ : >

Re: syncdb error with Mysql database on Windows 7

I also followed note for create schema ( have watched https://www.youtube.com/watch?v=EL39BGSUkzw video in addition ) and got success. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails

Re: syncdb error with Mysql database on Windows 7

For the record I solved this, I was mistaken there was no "mydb" schema in MySQL. I created this schema and ran the "syncdb" command without any problems. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop

Re: syncdb issue (begginer stuff)

On Mon, Aug 26, 2013 at 1:19 PM, Natko Perko wrote: > @laurent i guess it worked, but now i get the error no module named > wikicamp.wiki.. this is all the code i have so far.. make sure the folder containing wikicamp is inside your PATH so you don't get import errors. make sure there's an __in

Re: syncdb issue (begginer stuff)

@laurent i guess it worked, but now i get the error no module named wikicamp.wiki.. this is all the code i have so far.. from django.db import models # Create your models here. class Page(models.Model): name = models.CharField(maxlength="20", primary_key=True) content = models.T

Re: syncdb issue (begginer stuff)

for your environment: you should definitely look into this http://www.jeffknupp.com/blog/2012/02/09/starting-a-django-project-the-right-way/ if you're using mac also this http://hackercodex.com/guide/python-virtualenv-on-mac-osx-mountain-lion-10.8/ setup your settings.py http://www.rdegges.com/t

Re: syncdb issue (begginer stuff)

On 26/08/2013 14:34, Natko Perko wrote: Hi out there, I just dove into Django (literally) and had so many issues installing it and knowing where to start from that I don't even know how I made it this far, so i finally started working on a project by mimicing this tutorial http://showmedo.com/vi

Re: SyncDb doesn't create tables in database

You are right ! It looks that the table has been created the first time and i didn't saw the message. Concerning the nodeid, i thought that it would be generated automatically and incremented for each new created instance , isn't it ? And i noticed also that the graph was created while the

Re: SyncDb doesn't create tables in database

You are right ! It looks that the table has been created the first time and i didn't saw the message. Concerning the nodeid, i thought that it would be generated automatically and incremented for each new created instance , isn't it ? Thanks for the reply On Thursday, May 30, 2013 3:35:36

Re: SyncDb doesn't create tables in database

On Thu, May 30, 2013 at 1:46 PM, Anas wrote: > I am having Neo4Django in my django based application and trying to use two > databases at the sametime : Neo4j and PostGIS. So i configured settings.py > as suggested in the docs (http://neo4django.readthedocs.org) and models.py > as well. > > When i

Re: Syncdb hangs/stalls

Do you have any processes open that are holding locks on the DB? Maybe a 'manage.py shell'? -A On Sat, May 25, 2013 at 6:11 PM, Joshua Kehn wrote: > Everything was working up until a few hours ago. Then I tried setting up > South because I have a less than simple migration to do. Now I've tri

Re: SyncDB w/ MySQL - Has anyone seen an error like this?

To try and find more information, I erased the Django-created tables and re-ran syncdb again. This time, I turned verbosity on to 3 and piped all of my stdout to a text file. I actually did this first. However, here's the contents of the first one which includes everything up to the point of fa

Re: SyncDB w/ MySQL - Has anyone seen an error like this?

I should mention that I *did* convert all of my existing tables to InnoDB which hasn't helped at all. I don't have any weird configuration in my settings.py dealing with the database. As far as I can tell, all new tables created by syncdb are also InnoDB. -- You received this message because y

Re: Syncdb error with new 1.5rc1

As for my problem, I solved it by making manage.py migrate --fake But I don't know that is the best and good solution. So far it works somehow :) -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://

Re: Syncdb error with new 1.5rc1

I found out what I was doing wrong in my model. I was using UserManager without having 'is_active' and 'is_admin' fields. Solved! As with galgal's problem. I had no luck using South to migrate from auth_mixin to django 1.5. I am doing it manually =/ 2013/1/8 galgal > I also get strange error: >

Re: Syncdb error with new 1.5rc1

I also get strange error: https://groups.google.com/forum/#!topic/django-users/lVUZ3hClyUg On Monday, January 7, 2013 10:46:18 PM UTC+1, Thiago wrote: > > I used auth mixin before in my app, then made the changes to make it work > on the official Django with new custom user. > > The problem is t

Re: Syncdb error with new 1.5rc1

Basically, I am using Person class as my AUTH_USER_MODEL. I realized it was missing 'username' in REQUIRED_FIELDS. from django.contrib.auth.models import UserManager, AbstractBaseUser ... class Person(AbstractBaseUser): objects = UserManager() username = models.CharField(_('username'), ma

Re: Syncdb error with new 1.5rc1

On Tue, Jan 8, 2013 at 5:46 AM, Thiago Carvalho D' Ávila < thiagocav...@gmail.com> wrote: > I used auth mixin before in my app, then made the changes to make it work > on the official Django with new custom user. > > The problem is that, when I run on my new empty db: > python manage.py syncdb --a

Re: syncdb in GeoDjango tutorial

post the code to WorldBorder Model. Thanks -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.c

Re: syncdb is not creating auth tables

I worked it out. I had another settings.py file inside one of the apps which had auth inside INSTALLED APPS and it was being imported into the main settings file. -m On 21 September 2012 08:14, Mario Gudelj wrote: > Thanks Amyth, but that doesn't work. I delete the sqlite file that gets > creat

Re: syncdb is not creating auth tables

Thanks Amyth, but that doesn't work. I delete the sqlite file that gets created with syncdb and i still get the same error. The new db file gets created with some tables in it, but no auth tables. On Sep 20, 2012 5:44 PM, "Amyth Arora" wrote: > You've changed the models after the tables were init

Re: syncdb is not creating auth tables

You've changed the models after the tables were initially created. Delete the current database and create a new one. Then ->> syncdb. On Thu, Sep 20, 2012 at 1:01 PM, Mario Gudelj wrote: > Hi Djangoers, > > I'm sure I'm missing something simple but for the life of me I can not > figure this out.

Re: Syncdb is producing different databases on different machines.

I appreciate your help. Thank you. On Wednesday, September 12, 2012 11:28:44 AM UTC-6, Brian McKeever wrote: > > I actually figured it out. > > I created a new virtualenv on my development machine and installed the > requirements to it, and from that virtualenv, syncdb fails to install the > inv

Re: Syncdb is producing different databases on different machines.

I actually figured it out. I created a new virtualenv on my development machine and installed the requirements to it, and from that virtualenv, syncdb fails to install the invitationuser table. I guess whoever is in charge of the django-invitation repository introduced a bug without changing th

Re: Syncdb is producing different databases on different machines.

lol wtf. Perhaps the code on the production server isn't fully up to date? Did you check the database to ensure the table definitely doesn't already exist? Did you try running "manage.py sql" on the production server to see if the SQL is printed out for the missing table? Cal On Wed, Sep 12, 201

Re: Syncdb is producing different databases on different machines.

I am not using any database router. These are my database settings: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'my database name', 'USER': 'my admin name', 'HOST': 'localhost', 'PASSWORD' : 'my password' }

Re: Syncdb is producing different databases on different machines.

Are you using any sort of custom db router? (look for DATABASE_ROUTERS in settings). On Wed, Sep 12, 2012 at 5:05 PM, Brian McKeever wrote: > On my development machine, upon freshly creating my postgresql database, > when I run syncdb, it creates two invitation tables - > invitation_invitationke

Re: Syncdb Error With Oracle Database - IntegrityError Exception

Thanks, Ian, I did miss that. Bookmarked for future reference. On Saturday, September 1, 2012 3:16:38 PM UTC+10, Ian wrote: > > On Fri, Aug 31, 2012 at 10:03 PM, Jon Blake > > wrote: > > Querying column timestamp of view user_objects for tables, sequences and > > triggers appears to confirm my

Re: Syncdb Error With Oracle Database - IntegrityError Exception

I've just dropped and re-created my user account with required privileges, and all has gone as expected. Table auth_permission has 18 rows. At the point where I'm prompted to create a superuser account, I made the mistake of resizing my terminal window, which resulted in exception EOFError bein

Re: Syncdb Error With Oracle Database - IntegrityError Exception

On Fri, Aug 31, 2012 at 10:03 PM, Jon Blake wrote: > Querying column timestamp of view user_objects for tables, sequences and > triggers appears to confirm my understanding of what base.py does. I'll drop > and recreate my user account, and try again. I'll advise how this goes. Does > the Django d

Re: Syncdb Error With Oracle Database - IntegrityError Exception

Thanks, Ian and Amyth, for your responses. I encountered the CREATE TRIGGER privilege issue early in my trials with Django with the Oracle database back end - Django propagated an Oracle "insufficient privileges" exception. That was quickly sorted by granting the required privilege to my user a

Re: Syncdb Error With Oracle Database - IntegrityError Exception

On Friday, August 31, 2012 12:10:54 AM UTC-6, Amyth wrote: > > Hey Jon, > > I guess this is because of a bug in django. Django already has a open > ticket for this bug. Check it out > here > . > > As described in that ticket, the reason for the proble

Re: Syncdb Error With Oracle Database - IntegrityError Exception

Hey Jon, I guess this is because of a bug in django. Django already has a open ticket for this bug. Check it out here . On Fri, Aug 31, 2012 at 7:17 AM, Jon Blake wrote: > Just discovered Django and trying out the Django 1.4 tutorial with an > Oracle

Re: syncdb does not find model, but it does in the shell

On 6/06/2012 16:47, jmolmo wrote: > I think that you have to indicate app_label in your separate model > file > According to: > https://docs.djangoproject.com/en/1.4/ref/models/options/ > > class MyTestModel(models.Model): > field1=models.CharField(max_length=12) > field2=models.CharField(

Re: syncdb does not find model, but it does in the shell

+1 -- Nice find! On Wed, Jun 6, 2012 at 10:47 AM, jmolmo wrote: > I think that you have to indicate app_label in your separate model > file > According to: > https://docs.djangoproject.com/en/1.4/ref/models/options/ > > -- You received this message because you are subscribed to the Google Grou

Re: syncdb does not find model, but it does in the shell

I think that you have to indicate app_label in your separate model file According to: https://docs.djangoproject.com/en/1.4/ref/models/options/ class MyTestModel(models.Model): field1=models.CharField(max_length=12) field2=models.CharField(max_length=12) class Meta: app_label =

Re: syncdb does not find model, but it does in the shell

I'm pretty sure you can't have a folder named models and that your models file needs to be called models.py -- unless you use some sort of a 'hack' to work around it. I remember seeing a bug posted about this issue which was pretty easily google-able. I just don't remember the bug number off hand,

Re: syncdb not creating columns in postgresql database

Thanks for all the advice, I appreciate it. On Tue, May 15, 2012 at 3:22 AM, doniyor wrote: > sorry for bad advice.. i thought i could work,, > > Am Dienstag, 15. Mai 2012 08:52:35 UTC+2 schrieb lawgon: > >> On Mon, 2012-05-14 at 09:06 -0700, doniyor wrote: >> > delete your app from INSTALLED_AP

Re: syncdb not creating columns in postgresql database

sorry for bad advice.. i thought i could work,, Am Dienstag, 15. Mai 2012 08:52:35 UTC+2 schrieb lawgon: > > On Mon, 2012-05-14 at 09:06 -0700, doniyor wrote: > > delete your app from INSTALLED_APPS and syncdb, AND list it again in > > INSTALLED_APPS and syncdb again.. > > > > if it doesnot w

Re: syncdb not creating columns in postgresql database

You might want to look into using South http://south.aeracode.org/ At first i thought it was cool, then I needed to alter a table with important data on it, and that's when I saw it's usefulness. On Tue, May 15, 2012 at 9:52 AM, kenneth gonsalves wrote: > On Mon, 2012-05-14 at 09:06 -0700, don

Re: syncdb not creating columns in postgresql database

On Mon, 2012-05-14 at 09:06 -0700, doniyor wrote: > delete your app from INSTALLED_APPS and syncdb, AND list it again in > INSTALLED_APPS and syncdb again.. > > if it doesnot work, do this: > > delete your db, then syncdb, then list your app in INSTALLED_APPS and > syncdb again. this is bad

Re: syncdb not creating columns in postgresql database

delete your app from INSTALLED_APPS and syncdb, AND list it again in INSTALLED_APPS and syncdb again.. if it doesnot work, do this: delete your db, then syncdb, then list your app in INSTALLED_APPS and syncdb again. Am Montag, 14. Mai 2012 17:54:35 UTC+2 schrieb Mac: > > Every time I edit

Re: syncdb failure in new project with 1.4c2

On Sat, Mar 17, 2012 at 3:16 PM, Thomas Lockhart wrote: > locale.getdefaultlocale() should return something other than (None,None) if > environment variables are set but istm that this should fail gracefully (or > not fail at all; the ticket suggests a solution using a different call which > does

Re: syncdb not creating join table

Looks like a m2m class can be identified by the ._meta.auto_created attribute, which also holds the class with the m2m field. So the router can check for attributes on that class. On Wed, Jan 4, 2012 at 11:49 AM, Brian Craft wrote: > I strongly suspect the problem I'm having has to do with databa

Re: syncdb not creating join table

I strongly suspect the problem I'm having has to do with database routers. It looks like under the hood django creates a model to represent the m2m relationship, and the router is blocking the syncdb for the generated model. I was using a class attribute on my models to control the routing, but I

Re: syncdb not finding and syncing my MySQL database

To clarify the I entered the command "python manage.py syncdb" from the the terminal prompt (current directory) which is consistent with my apps directory. Manage.py is in the project root and executes because its in my search path. I am currently at my day job so I am not able to send the trace-

Re: syncdb not finding and syncing my MySQL database

Yes, please offer more details. One thing I noticed off the bat, though, was that you said you are running "python manage.py syncdb" from the directory where your models.py is. The manage.py file is at the root of your project, not in the apps folder(s) where models.py is. Furbee On Mon, Nov 21,

Re: syncdb not finding and syncing my MySQL database

Hi, "I am getting an error" This is not a proper way to ask question. Please post your trace-back somewhere and send the link to the group or at least specify what error is it, so that, we could help you. Thanks, Anoop atm ___ Life is short, Live it hard. On 21 November 2011 23:31, BillB1951

Re: syncdb for mysql using engine=NDBCLUSTER

Hi Florian, Thanks for the pointer.. nice and works like a charm.. i will prefer add the options in the settings.py as the table will growing and work for all application table including admin table. and the next target is figure out about the database router for load balancing the sql query..

Re: syncdb for mysql using engine=NDBCLUSTER

Oh and if you don't want to create all tables in the cluster, just create with the default engine and then switch as needed. -- 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/m

Re: syncdb for mysql using engine=NDBCLUSTER

Hi, this can be done as documented like for the innodb backend: https://docs.djangoproject.com/en/dev/ref/databases/#creating-your-tables Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit

Re: syncdb error

Thank you Karen, Those links are really helpful Phage -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@g

Re: syncdb error

On Tue, Jun 21, 2011 at 11:24 PM, T4 Phage wrote: > Hello! > > When I run syncdb it returns an error ending in > "_mysql_exceptions.OperationalError: (1050, "Table 'people_person' > already exists")." I know that the table 'people_person' already > exists because I used syncdb to make it earlier

Re: syncdb doesn't create UserProfile table

On Tue, 2011-06-21 at 12:49 +0100, Tom Evans wrote: > >> It will still work perfectly with ForeignKey(unique=True), > > > > the docs say one2one > > > > That doesn't negate my statement. > > You said that User.get_profile() will only work with OneToOneField, > which is incorrect, it will also wor

Re: syncdb doesn't create UserProfile table

On Sat, Jun 18, 2011 at 8:27 AM, Kenneth Gonsalves wrote: > On Thu, 2011-06-16 at 12:13 +0100, Tom Evans wrote: >> On Thu, Jun 16, 2011 at 11:55 AM, Kenneth Gonsalves >> wrote: >> > those entries are old. The point is that the built in >> User.get_profile() >> > only works with onetoone. The diff

Re: syncdb doesn't create UserProfile table

On Thu, 2011-06-16 at 12:13 +0100, Tom Evans wrote: > On Thu, Jun 16, 2011 at 11:55 AM, Kenneth Gonsalves > wrote: > > those entries are old. The point is that the built in > User.get_profile() > > only works with onetoone. The difference is in the reverse lookup. > > That is not correct. > > It

Re: syncdb doesn't create UserProfile table

On Thu, Jun 16, 2011 at 11:55 AM, Kenneth Gonsalves wrote: > those entries are old. The point is that the built in User.get_profile() > only works with onetoone. The difference is in the reverse lookup. That is not correct. It will still work perfectly with ForeignKey(unique=True), it is just be

Re: syncdb doesn't create UserProfile table

On Thu, 2011-06-16 at 12:24 +0200, Ivo Brodien wrote: > This Django Book however is old and in the new one in Chapter 14: > Sessions, Users, and Registration the User Profile does not get > mentioned anymore. > > Also the first search result in google for “django user profile” is > James Bennetts

Re: syncdb doesn't create UserProfile table

> In the paragraph preceding this link it explicitly states to use > OneToOneField. The Django documentation is canonical, if it says one > thing, and elsewhere on the internet says something else, the internet > is wrong. The internet is often wrong. > > The difference between a ForeignKey(unique

Re: syncdb doesn't create UserProfile table

On Thu, Jun 16, 2011 at 11:24 AM, Ivo Brodien wrote: > > Actually, I've read that ForeignKey is now the way to specify it. > > unique foreign key *was* the correct way as onetoone was broken. This is > no longer true. > > where is the most up to date info on this? > In the dev docs about storing a

Re: syncdb doesn't create UserProfile table

>> Actually, I've read that ForeignKey is now the way to specify it. > > unique foreign key *was* the correct way as onetoone was broken. This is > no longer true. where is the most up to date info on this? In the dev docs about storing additional user info on djangoproject.com there is a lin

Re: syncdb doesn't create UserProfile table

On 16/06/2011 11:29, Kenneth Gonsalves wrote: > On Thu, 2011-06-16 at 11:10 +0200, Benedict Verheyen wrote: >> On 16/06/2011 10:43, Kenneth Gonsalves wrote: >>> On Thu, 2011-06-16 at 10:10 +0200, Benedict Verheyen wrote: user = models.ForeignKey(User, unique=True) >>> >>> you need onetoone for

Re: syncdb doesn't create UserProfile table

On Thu, 2011-06-16 at 11:10 +0200, Benedict Verheyen wrote: > On 16/06/2011 10:43, Kenneth Gonsalves wrote: > > On Thu, 2011-06-16 at 10:10 +0200, Benedict Verheyen wrote: > >> user = models.ForeignKey(User, unique=True) > > > > you need onetoone for this to work. > > Hi, > > Actually, I've read

Re: syncdb doesn't create UserProfile table

On 16/06/2011 10:43, Kenneth Gonsalves wrote: > On Thu, 2011-06-16 at 10:10 +0200, Benedict Verheyen wrote: >> user = models.ForeignKey(User, unique=True) > > you need onetoone for this to work. Hi, Actually, I've read that ForeignKey is now the way to specify it. Anyway, the problem has been so

Re: syncdb doesn't create UserProfile table

On 16/06/2011 10:27, Ivo Brodien wrote: > an idea: Do you have a __init__.py in every subfolder? also the models and > userprofile folder under calltracking_main ? > > Ivo, i do have an __init__.py in every folder. As Jari pointed out, it was the appname in my UserProfile model that was incor

Re: syncdb doesn't create UserProfile table

On 16/06/2011 10:25, Jani Tiainen wrote: > On Thu, 2011-06-16 at 10:10 +0200, Benedict Verheyen wrote: >> Hi, >> >> >> The syncdb command doesn't want to create the UserProfile table. >> Also when I was trying to get this working while running the app, >> it was complaining about AUTH_PROFILE_MODUL

Re: syncdb doesn't create UserProfile table

On Thu, 2011-06-16 at 10:10 +0200, Benedict Verheyen wrote: > user = models.ForeignKey(User, unique=True) you need onetoone for this to work. -- regards KG http://lawgon.livejournal.com Coimbatore LUG rox http://ilugcbe.techstud.org/ -- You received this message because you are subscribed to th

Re: syncdb doesn't create UserProfile table

an idea: Do you have a __init__.py in every subfolder? also the models and userprofile folder under calltracking_main ? On Jun 16, 2011, at 10:10 AM, Benedict Verheyen wrote: > Hi, > > > The syncdb command doesn't want to create the UserProfile table. > Also when I was trying to get this wor

Re: syncdb doesn't create UserProfile table

On Thu, 2011-06-16 at 10:10 +0200, Benedict Verheyen wrote: > Hi, > > > The syncdb command doesn't want to create the UserProfile table. > Also when I was trying to get this working while running the app, > it was complaining about AUTH_PROFILE_MODULE. > It is however correctly specified in my se

Re: syncdb just hangs/tutorial

Check out once properly yor connection(Host, username,password,port) in setting.py On Apr 11, 6:08 pm, L Corbani wrote: > I am new to django, and am running the tutorial.  I have edited > 'settings.py' and am running "python manage.py runserver". > > When I run the server and then call "python

Re: syncdb just hangs/tutorial

Postgres uses a unix style user model. Its intuitive once you understand it: I would seriously advise you to read the tutorial for this: http://www.postgresql.org/docs/manuals/ FInd out the version you are using too. Specifically: 1.2. Architectural Fundamentals onwards. That error just means

Re: syncdb just hangs/tutorial

Shawn, In fact, it was an issue with my database settings. I changed the host and now it is working. Thanks for helping me shift my brain a bit this morning :) Lori On Apr 11, 9:31 am, Shawn Milochik wrote: > Try it with sqlite3. If that works, then the problem is probably with > your Postg

Re: syncdb just hangs/tutorial

Can you provide information on what OS you are using? It may just be a configuration issue. I had to edit the postgresql pg_hba.conf file on my ubuntu setup to make it less strict (for development purposes). https://help.ubuntu.com/community/PostgreSQL read on 'managing the server' section to get a

Re: syncdb just hangs/tutorial

Try it with sqlite3. If that works, then the problem is probably with your Postgres setup. Try interacting with Postgres using the psql command. It's likely that you have some problem in the configuration. -- You received this message because you are subscribed to the Google Groups "Django user

Re: syncdb problem - windows, sqlite

Nick. Thank you Sir. Man does another set of eyes help! On Wed, Sep 15, 2010 at 12:11 PM, Nick < iregisteratwebsiteswitht...@gmail.com> wrote: > This seems to happen when you specify an incorrect path to the > database in NAME. > > Fix: > Use the correct path. :D > > It looks like you spelled 'fr

Re: syncdb problem - windows, sqlite

This seems to happen when you specify an incorrect path to the database in NAME. Fix: Use the correct path. :D It looks like you spelled 'frameworks' incorrectly. On Sep 15, 12:03 pm, Aju wrote: > Hi, > > I am using the Django tutorial (Windows xp, python 2.5.4, django 1.2.3) and > am facing a

Re: syncdb on Django

On Wed, 2010-09-15 at 13:44 +0800, Odkoo Ch wrote: > django.core.exceptions.ImproperlyConfigured: You haven't set the > database > ENGINE setting yet. what version of django? In the current version you need: 'ENGINE': 'django.db.backends.mysql' -- regards Kenneth Gonsalves -- You received this

Re: syncdb on Django

On Wed, Sep 15, 2010 at 7:34 AM, Roderick wrote: > ENGINE should be set to 'django.db.backends.mysql' not 'mysql', if you > are using mysql. > > I believe the shorthand names are still accepted, so I don't think that is the problem. Rather it appears a pre-1.2 version of Django may be in use. Tha

Re: syncdb on Django

ENGINE should be set to 'django.db.backends.mysql' not 'mysql', if you are using mysql. On Sep 15, 1:44 am, Odkoo Ch wrote: > Hello. everyone > > help me > > DATABASES = { >     'default': { >         'ENGINE': 'mysql',  # Add 'postgresql_psycopg2', 'postgresql', > 'mysql', 'sqlite3' or 'oracle'.

Re: syncdb always indicates there are no fixtures

Tx a lot "Restless"... As yr post took me a while to decipher it and get most of the info, I thought it might be usefull to post extra info based on yr post. Django allows for extension to the command line (./manage.py). One of the extension is provided by Google : http://code.google.com/p/django-

Re: syncdb always indicates there are no fixtures

On 11 Cze, 12:19, tsmets wrote: > The problem was just the naming convention ... > They should have been named initial_data.json as mentionned in the URL > provided by Xavier. > > Any help on how to run python scripts directly to create my data > sets ? > What I do now is fine but could be be

Re: syncdb always indicates there are no fixtures

On Fri, Jun 11, 2010 at 6:19 AM, tsmets wrote: ... > > Any help on how to run python scripts directly to create my data > sets ? > What I do now is fine but could be better automated ? > ... One possibility is to write yourself one or more management commands which you could invoke by hand,

Re: syncdb always indicates there are no fixtures

I have a XML fixture with the language codes if you need it: http://pastebin.com/U4cAxXzY On Fri, Jun 11, 2010 at 12:19, tsmets wrote: > The problem was just the naming convention ... > They should have been named initial_data.json as mentionned in the URL > provided by Xavier. > > > Any help o

Re: syncdb always indicates there are no fixtures

The problem was just the naming convention ... They should have been named initial_data.json as mentionned in the URL provided by Xavier. Any help on how to run python scripts directly to create my data sets ? What I do now is fine but could be better automated ? [code] from sportotop.Base

Re: syncdb always indicates there are no fixtures

¿Are you setting the variable FIXTURES_DIR in settings.py? On Fri, Jun 11, 2010 at 12:03, Kenneth Gonsalves wrote: > On Friday 11 June 2010 14:20:59 tsmets wrote: > > But I have json's files in multiple "fixtures" directories. > > [code] > > Thomas-SMETSs-MacBook-Pro:sportotop tsmets$ find . -ty

Re: syncdb always indicates there are no fixtures

On Friday 11 June 2010 14:20:59 tsmets wrote: > But I have json's files in multiple "fixtures" directories. > [code] > Thomas-SMETSs-MacBook-Pro:sportotop tsmets$ find . -type f -name > "*.json" | grep -v "\.svn" > ./Base/fixtures/Sports.json > ./fixtures/Base-with-UserProfilesAndClubsNoAddresses.j

Re: syncdb always indicates there are no fixtures

Hello, Fixtures are described in the documentation, especially there: http://docs.djangoproject.com/en/dev/howto/initial-data/#automatically-loading-initial-data-fixtures You have to follow the name convention to get them automatically loaded. Regards, Xavier. -- You received this message beca

Re: syncdb error for models pointing to each other

On 26 March 2010 01:11, Ramiro Morales wrote: > On Thu, Mar 25, 2010 at 9:03 PM, Dries Desmet wrote: > > My models are: > > > > > > class Album(models.Model): > > slug = models.SlugField( > > unique=True, > > help_text=_("Suggested value automatically generated from titl

Re: syncdb error for models pointing to each other

On Thu, Mar 25, 2010 at 9:03 PM, Dries Desmet wrote: > My models are: > > > class Album(models.Model): >     slug = models.SlugField( >     unique=True, >     help_text=_("Suggested value automatically generated from title. > Must be unique.") >     ) >     # using name of the mod

Re: syncdb for INSTALLED_APPS throws errors

Thank You --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr..

Re: syncdb for INSTALLED_APPS throws errors

The warning on line 2 is because you are using python2.6, default in Ubuntu9.04. You don't need to worry about it. It is just telling the authors of mysqldb that ImmutableSet is going away in newer versions of python. Not something you need to care about. On Oct 29, 3:37 am, sridharpandu wrote:

Re: syncdb for INSTALLED_APPS throws errors

Skylar Thanks. It works. Here is the trace. Should warning on line 2 be ignored? srid...@sridhar:~$ python manage.py syncdb /var/lib/python-support/python2.6/MySQLdb/__init__.py:34: DeprecationWarning: the sets module is deprecated from sets import ImmutableSet Creating table auth_permission C

Re: syncdb for INSTALLED_APPS throws errors

If you are not in a virtualenv with -no-site-packages then you should be able to just: sudo aptitude install python-mysqldb sridharpandu wrote: > Thanks. That was quick. I use Ubuntu 9.04 (jaunty). I am unable to > figure out the location of MySQLdb. A "WHEREIS MySQLdb" at the command > prompt

Re: syncdb for INSTALLED_APPS throws errors

Thanks. That was quick. I use Ubuntu 9.04 (jaunty). I am unable to figure out the location of MySQLdb. A "WHEREIS MySQLdb" at the command prompt returned MySQLdb: Is there a way to figure out Best regards Sridhar On Oct 29, 12:07 pm, Kenneth Gonsalves wrote: > On Thursday 29 Oct 2009 12:17:56

Re: syncdb for INSTALLED_APPS throws errors

On Thursday 29 Oct 2009 12:17:56 pm sridharpandu wrote: > raise ImproperlyConfigured("Error loading MySQLdb module: %s" % e) > django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb > module: No module named MySQLdb > you need MysSQLdb to connect to the database, either it is not in

Re: syncdb for INSTALLED_APPS throws errors

On Thu, Oct 29, 2009 at 2:47 PM, sridharpandu wrote: > > Hi, > > I ran the syncdb command to create the tables for INSTALLED_APPS. I > get the errors as shown in the output below. Can someone tell me > what's wrong. I am using a laptop that runs Django as well as the > MySQL database . > > srid...

  1   2   3   >