Thanks russ I greatly appreciate it!, I'll just wait for the fix.
cheers,
james
On Jul 22, 11:01 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 7/22/07, james_027 <[EMAIL PROTECTED]> wrote:
>
>
>
> > the profile table's dell has constraint clause in it, while the
> > cellusage table h
On 7/22/07, james_027 <[EMAIL PROTECTED]> wrote:
>
> the profile table's dell has constraint clause in it, while the
> cellusage table has no constraint clause only key clause is only tells
> that it is index.
That appears to be the effect of ticket #2720 [1] that I mentioned
earlier. The foreign
Hi russ,
nice to hear from you again...
As of now I am only saying that no foreign key is created by just
checking the database tables itself, I haven't perform any django
query.
doing the describe main_profile and main_cellusage I got the same
results ... but for me the MUL value on Key column
On 7/22/07, james_027 <[EMAIL PROTECTED]> wrote:
>
> 5. then i run python manage.py syncdb
>
> the result is ... in my cellusage table there is no foreign key
> created. but in the profile table there is a foreign created.
>
mysql> describe mytest_profile;
++-+--+-
hi,
in the case of my application here is what i done (I start from
scratch):
1. django-admin.py startproject ksk
2. django-admin.py startapp main
3. edit the settings.py file: database engine, name, user, password,
password, and then add the ksk.main in the installed_apps
INSTALLED_APPS = (
On 7/21/07, james_027 <[EMAIL PROTECTED]> wrote:
>
> I dont know what you mean by what_I_have_done?
Help me to replicate exactly the steps that you have taken to make
this problem occur. I have your model file. If _I_ use that model
file, and it works fine for me. Obviously you have done somethin
Hi,
I dont know what you mean by what_I_have_done?
I just follow the django tutorial. the one with poll and choice model.
I did every step. and that's my result.
However I have discover something
this setting
INSTALLED_APPS = (
'django.contrib.admin',
'django.contrib.auth',
'd
On 7/21/07, james_027 <[EMAIL PROTECTED]> wrote:
>
> I didn't say that the relation aren't working, I just wondering why
> foreign key wasn't created in my case. I am using both SQL Manager
> 2005 lite and MySQL Administrator just to take a look at the table
> created.
When I run your example, th
I didn't say that the relation aren't working, I just wondering why
foreign key wasn't created in my case. I am using both SQL Manager
2005 lite and MySQL Administrator just to take a look at the table
created.
any idea?
james
On Jul 21, 11:16 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote
On 7/21/07, james_027 <[EMAIL PROTECTED]> wrote:
>
> I am doing this in winxp , mysql 5 , python 2.5 , latest mysql driver
> for python. Hope I've provided enough info.
Not even close.
Perhaps I'm not being clear. I have tried your example. It works for
me. The fact that many thousands of other
Hi,
The table was created fine with only a small problem and it's the
foreign key. I have my application listed on settings.py, code my
model on models.py, then perform manage.py syncdb my_app as I am aware
that if the table exist it wont recreate it. I did a number of times
of deleting my tables
On 7/21/07, james_027 <[EMAIL PROTECTED]> wrote:
>
> When the relationship is within the same namespace (am I using the
> right term, pls correct me) the manage.py syncdb create the tables
> without a problem if all the tables are create on the same time, but
> if the tables weren't created the sa
12 matches
Mail list logo