On Wed, 2006-07-05 at 01:59 +, DavidA wrote:
>
> Malcolm Tredinnick wrote:
> > On Tue, 2006-07-04 at 02:11 +, DavidA wrote:
> > I'm not sure a created() method is going to be the right API, since this
> > event has very transitory relevance, but your example does suggest we
> > may need
you can specify what user/password to connect to database in
settings.py file, under your project dir
http://www.djangoproject.com/documentation/tutorial1/#database-setup
On 7/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I am in the process of moving my Django project from using the
>
One related question on nullable foreign keys: does the Django ORM
always use inner/left joins for select_related() calls? If so, null FKs
will cause rows to be excluded from a query so you may have to handle
these with direct SQL.
Personally, I often create an "unknown" row in a table (and do a
thanx
On 7/4/06, Jan Claeys <[EMAIL PROTECTED]> wrote:
>
> On ma, 2006-06-26 at 22:26 -0300, Douglas Campos wrote:
> > does anyone have some light for me? I'm new to this ubuntu thing
> >
> > I want to mantain a nightly .deb build from django svn, to help the poor
> > (tm)
>
> There is a
Malcolm Tredinnick wrote:
> On Tue, 2006-07-04 at 02:11 +, DavidA wrote:
> I'm not sure a created() method is going to be the right API, since this
> event has very transitory relevance, but your example does suggest we
> may need something extra here at some point.
I agree that created()
On ma, 2006-06-26 at 22:26 -0300, Douglas Campos wrote:
> does anyone have some light for me? I'm new to this ubuntu thing
>
> I want to mantain a nightly .deb build from django svn, to help the poor (tm)
There is a packaging guide in the included help (System --> Help -->
first item there) as
On 07/05/06 03:34, Iain Duncan wrote:
> I stumbled on some behaviour that I'm sure is explained somewhere but
> not in the tutorials so I haven't found it.
>
> I made a global log object for debugging. I noticed instantiating
> objects in the view global name space executes before anything else
Currently the only AJAX and Django documentation, that I know of, is
at:
http://code.djangoproject.com/wiki/AjaxDjangoDojoForm
I've never really worked w/ AJAX validation, so I'm not sure how hard
it would be to expand on those 3 tutorials to allow it. I'm currently
experimenting with AJAX and
I'd love to see some good examples of form validation using AJAX and Django.
Field-by-field AJAX(J) validation as well as final-submit validation (also
could be done via AJAX(J)) examples are needed.
TIA,
Scott
--~--~-~--~~~---~--~~
You received this message
On Jul 4, 2006, at 11:34 AM, Jorge Gajon wrote:
> The odd thing is that the FormWrapper, when rendering the select
> field, will pre-select the country according to the value in
> new_data['country_id'] instead of new_data['country']. But when the
> form is POSTed to the view, the selected value
>>foo = models.ForeignKey( bar, null=True, blank=True )
>
>
> Give this one a go again. This is the form that should work. Perhaps
> there was another problem that got in the way? BTW there is nothing
> wrong with using a null field for your foreign key relationship in most
> schemas, from a
One of my very few gripes with the otherwise amazing admin interface is
the way deletions are handled when foreign key relationships are there.
If you want to delete one item, it takes out any others depending on
this item. Makes sense in a way, but could be very dangerous in the
hands of a
I stumbled on some behaviour that I'm sure is explained somewhere but
not in the tutorials so I haven't found it.
I made a global log object for debugging. I noticed instantiating
objects in the view global name space executes before anything else in
the views module on page load, very useful
>>Well... Mod_python is the easiest method of running django, FastCGI
>>setup is more advanced and usually requires basic knowledge about
>>forking vs. threading, writing init scripts etc. These are things that
>>makes it harder for beginners to understand Django itself so in my
>>opinion it's
On 04/07/06, Spider <[EMAIL PROTECTED]> wrote:
>
> Can someone explan to me the underlying concept behind the distinction
> between django "projects" and "applications"?
>
> I know that an application is part of a project, and it's many-to-many,
> so an app can be part of more than one project,
Can someone explan to me the underlying concept behind the distinction
between django "projects" and "applications"?
I know that an application is part of a project, and it's many-to-many,
so an app can be part of more than one project, and a project can
contain more than one app. But what to
I am in the process of moving my Django project from using the
development server to Apache and mod_python. I created the PostgreSQL
databases as myself and ran the development server as myself. Now that
I'm getting stuff going with mod_python, it'll start running as user
"www-data" under
Hi Todd,
> > and for a ForeignKey:
> > related_object = OtherObject.objects.get(pk=23)
> > new_data['related_object'] = str(related_object.id)
>
> This, not so much. The related object entry is in the data field of
> the FormWrapper when I look at it, but if I render the SelectField it
>
I'm following the tutorial:
http://www.djangoproject.com/documentation/tutorial2/
And I couldn't get the admin working by just uncommenting the
"Uncomment this for admin:" line.
My project name is "rico", I had to change the url to "rico/admin/"
instead of only "admin/".
This way I can log
thx jay, recalling the saved objects from session can be from any
function.
the second point is solved, dont worry.thx again
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this
On 7/4/06, bernadet <[EMAIL PROTECTED]> wrote:
>
> hii,
>
> now i have another question related to the session:
> if i save an object to the session from a certain view
> (request.session['myperson']=new_person), can i recall it from another
> view by request.session['myperson']. ( i mean from 2
I think that a "official translation team" would be awesome. If we can
concentrate the resources, noobs will find their way easily
On 7/4/06, Frankie Robertson <[EMAIL PROTECTED]> wrote:
>
> No, I would like to see a unified effort, if you look at the comments
> for a lot of the documentation
No, I would like to see a unified effort, if you look at the comments
for a lot of the documentation you'll find links to translations into
the commenters native tounge. It would be nice to see what the core
team had to say about this.
On 03/07/06, Douglas Campos <[EMAIL PROTECTED]> wrote:
> Is
Carlos Yoder wrote:
>>> Can anybody confirm having a Django app running under Apache 1.x +
>>> FastCGI? Is this actually a silly question, since let's say Dreamhost
>>> gives only Apache 1.x support? :-)
>> i have a website served by apache 1.x + fastcgi. no problems.
>>
>> gabor
>
> Thank you
> > Can anybody confirm having a Django app running under Apache 1.x +
> > FastCGI? Is this actually a silly question, since let's say Dreamhost
> > gives only Apache 1.x support? :-)
>
> i have a website served by apache 1.x + fastcgi. no problems.
>
> gabor
Thank you very much, or should I say
On Tue, 2006-07-04 at 09:19 +0200, toth anna wrote:
> I asked you before about how to implement "cointainer level
> logic" in django.
> You suggested me to override save() method (example was:
> object can decide from the "fields" to create more "records"
> instead just saving oneself). It worked
> > I wonder if more people were/are confused by that sentence (found
> > here: http://www.djangoproject.com/documentation/install/)...?
>
> Well... Mod_python is the easiest method of running django, FastCGI
> setup is more advanced and usually requires basic knowledge about
> forking vs.
Carlos Yoder wrote:
> I wonder if more people were/are confused by that sentence (found
> here: http://www.djangoproject.com/documentation/install/)...?
Well... Mod_python is the easiest method of running django, FastCGI
setup is more advanced and usually requires basic knowledge about
forking
>> Hello people!
>> Since I only found *one* place stating that Django "requires Apache
>> 2.x and mod_python 3.x", I felt I should check :-)
>> Just to be absolutely sure... Django does NOT work under Apache 1.x, correct?
> Not correct. This 2.0 thing is mentioned because Django works under
>
Carlos Yoder wrote:
> Hello people!
>
> Since I only found *one* place stating that Django "requires Apache
> 2.x and mod_python 3.x", I felt I should check :-)
>
> Just to be absolutely sure... Django does NOT work under Apache 1.x, correct?
Not correct. This 2.0 thing is mentioned because
I asked you before about how to implement "cointainer level
logic" in django.
You suggested me to override save() method (example was:
object can decide from the "fields" to create more "records"
instead just saving oneself). It worked well, but...
What do you suggest if i have to interact with
hii,
now i have another question related to the session:
if i save an object to the session from a certain view
(request.session['myperson']=new_person), can i recall it from another
view by request.session['myperson']. ( i mean from 2 different
functions)
and please according to link the user
> foo = models.ForeignKey( bar, null=True, blank=True )
Give this one a go again. This is the form that should work. Perhaps
there was another problem that got in the way? BTW there is nothing
wrong with using a null field for your foreign key relationship in most
schemas, from a practical
Hello people!
Since I only found *one* place stating that Django "requires Apache
2.x and mod_python 3.x", I felt I should check :-)
Just to be absolutely sure... Django does NOT work under Apache 1.x, correct?
I'm tring to setup a Django env at Servage.net, and they provide
Apache 1.x,
34 matches
Mail list logo
