Re: Tutorial for MR

2006-05-05 Thread Luke Plant
On Friday 05 May 2006 11:39, Honza Král wrote: > I agree, but at least it works... > it would be nice to have this at least at a module level... Yeah, I was thinking about doing that, or some other nice solution. Ideally it would handle it invisibly, but once you get into it, it's a slightly

Re: Tutorial for MR

2006-05-05 Thread Honza Král
I agree, but at least it works... it would be nice to have this at least at a module level... On 5/5/06, DavidA <[EMAIL PROTECTED]> wrote: > > But for every model? Sounds a little kludgy to have to add that to > every model just to break them into separate files. > > > > > -- Honza Král E-Mail:

Re: Tutorial for MR

2006-05-04 Thread DavidA
But for every model? Sounds a little kludgy to have to add that to every model just to break them into separate files. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,

Re: Tutorial for MR

2006-05-04 Thread Luke Plant
On Wednesday 03 May 2006 23:52, Luke Plant wrote: > /myproject > /myapp > /models > __init__.py > foo.py > bar.py > > > In __init__.py, I have: > -- > from foo import Foo, SomeThingElse > from bar import Bar, AnotherSomething > # a few

Re: Tutorial for MR

2006-05-04 Thread Beorn
I submitted a ticket about this (I believe) 2 weeks ago: http://code.djangoproject.com/ticket/1658 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to

Re: Tutorial for MR

2006-05-03 Thread Honza Král
On 5/4/06, Luke Plant <[EMAIL PROTECTED]> wrote: > > On Wednesday 03 May 2006 15:39, Malcolm Tredinnick wrote: > > On Wed, 2006-05-03 at 16:29 +0200, Honza Král wrote: > > > BEGIN; > > > COMMIT; > > > is the output of manage.py sql app (empty sql script for > > > postgreSQL) > > > > > > I am

Re: Tutorial for MR

2006-05-03 Thread Luke Plant
On Wednesday 03 May 2006 15:39, Malcolm Tredinnick wrote: > On Wed, 2006-05-03 at 16:29 +0200, Honza Král wrote: > > BEGIN; > > COMMIT; > > is the output of manage.py sql app (empty sql script for > > postgreSQL) > > > > I am fairly new to python, so I completely don't mind trivial > > questions,

Re: Tutorial for MR

2006-05-03 Thread Honza Král
I did manage to get this working by a quick change to django.db.models.loading.py where on line 40 in get_models() i changed _app_models.get(app_mod.__name__.split(.)[-2], {}).values() to _app_models.get(app_mod.__name__.split(.)[-1], {}).values() I do not know, whether it is a right thing to

Re: Tutorial for MR

2006-05-03 Thread Honza Král
I was getting worried that I didn't get some basic fact, thank you for your help On 5/3/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > On Wed, 2006-05-03 at 16:29 +0200, Honza Král wrote: > > BEGIN; > > COMMIT; > > is the output of manage.py sql app (empty sql script for postgreSQL) > > >

Re: Tutorial for MR

2006-05-03 Thread Malcolm Tredinnick
On Wed, 2006-05-03 at 16:29 +0200, Honza Král wrote: > BEGIN; > COMMIT; > is the output of manage.py sql app (empty sql script for postgreSQL) > > I am fairly new to python, so I completely don't mind trivial questions, > in app/models/__init__.py I have: > > # base models > from

Re: Tutorial for MR

2006-05-03 Thread Michael Radziej
Honza Král wrote: > Yes, when I have all my model classes in file models.py, manage.py sql > works just fine > > when I split my models into two or more files and put them into models > subdirectory (with __init__.py containing the proper __all__ list), it > does not work: > BEGIN > COMMIT; > >

Re: Tutorial for MR

2006-05-03 Thread Honza Král
On 5/3/06, Michael Radziej <[EMAIL PROTECTED]> wrote: > > Honza Král wrote: > > Thank you, I went to that page, but, for reasons unknown to me > > (perhaps brain death), didn't check the status of the tutorials... :-/ > > > > as for my other inquiry, can anyone tell me if it is possible to have >

Re: Tutorial for MR

2006-05-03 Thread Michael Radziej
Honza Král wrote: > Thank you, I went to that page, but, for reasons unknown to me > (perhaps brain death), didn't check the status of the tutorials... :-/ > > as for my other inquiry, can anyone tell me if it is possible to have > models spread through multiple files? I am afraid I have also

Re: Tutorial for MR

2006-05-03 Thread Honza Král
Thank you, I went to that page, but, for reasons unknown to me (perhaps brain death), didn't check the status of the tutorials... :-/ as for my other inquiry, can anyone tell me if it is possible to have models spread through multiple files? I am afraid I have also missed something trivial, but I

Re: Tutorial for MR

2006-05-03 Thread CoolGoose
http://code.djangoproject.com/wiki/RemovingTheMagic#Documentationstatus As you can see the tutorials aren't proofread yet --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,

Tutorial for MR

2006-05-02 Thread Honza Král
Hello all, I tried to port my sample application to magic-removal (now AKA trunk) and it stopped working, because I had my model split into many files... when I merge these files ( cat models/*.py > models.py) everything (ehm, python manage.py sql APP ) worked. If this is the correct way to do