On 5/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> it is very difficult to select a record for a 1:n relation from a drop
> down listbox if the related table contains many (in my case 3000 today)
> records. is it possible to tell the admin fe to give a nice selection
> window with the us
On 5/9/06, DavidA <[EMAIL PROTECTED]> wrote:
> Can't you just accomplish the same goal by adding a couple of lines to
> your settings file? Assuming you had an environ variable DSN set like
> this:
> [...]
> I guess it just seems like its easy enought to do in Python directly,
> why would you need
On 5/9/06, pbx <[EMAIL PROTECTED]> wrote:
> Here's another way to look at it, given that we are still at 0.91+:
> Besides inertia, what are the arguments in favor of the system Django
> currently uses? The only person I've seen address this is Jacob, who
> correctly noted in the ticket comments th
Here's another way to look at it, given that we are still at 0.91+:
Besides inertia, what are the arguments in favor of the system Django
currently uses? The only person I've seen address this is Jacob, who
correctly noted in the ticket comments that some beginners would find
the separate settings
Hi.
I have the following model:
class User(models.Model):
id_user = models.AutoField(primary_key = True)
username = models.CharField(maxlength = 30, unique = True, null =
True)
name = models.CharField(maxlength = 50, unique = True)
class Meta:
db_t
Can't you just accomplish the same goal by adding a couple of lines to
your settings file? Assuming you had an environ variable DSN set like
this:
DSN=ENGINE=mysql;NAME=data;USER=root;PASSWORD=redpill;HOST=localhost
then add:
import os
dsn = dict([kv.split('=') for kv in os.environ['DSN'].split
Hi,
I've hacked my way into the admin filters, changing the
RelatedFilterSpec from a single-select filter to a multi-select filter.
I can now filter on multiple values from the same ManyToMany or
ForeignKey relationship, i.e. if I add 'groups' to the list_filter for
Users, I can select all users
The logos at
http://www.djangoproject.com/community/logos/
particularaly
http://media.djangoproject.com/img/logos/django-logo-negative.png
don't seem to follow the "Official colors" the green in the background
is not RGB: R:9 G:46 B:32
Mistake? Coversion problem?
--~--~-~--~~
yes, raw_id_admin looks fine. i saw that but the description sounds as
i have to remember the pk and just can enter that by hand. thanks!
p.s.: perhaps the doc should mention that there is a search option if
this is set...
--~--~-~--~~~---~--~~
You received this
On 5/9/06, Kevin <[EMAIL PROTECTED]> wrote:
> I ran into this problem as well. The issue is that super() expects the
> child class not the parent class (the documentation is wrong),
Ah, thanks for pointing this out! I've corrected the docs.
Adrian
--
Adrian Holovaty
holovaty.com | djangoprojec
try the raw_id_admin option
On 5/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> it is very difficult to select a record for a 1:n relation from a drop
> down listbox if the related table contains many (in my case 3000 today)
> records. is it possible to tell the admin fe to give a nice sel
it is very difficult to select a record for a 1:n relation from a drop
down listbox if the related table contains many (in my case 3000 today)
records. is it possible to tell the admin fe to give a nice selection
window with the usual filter/sort possibilities?
--~--~-~--~~--
Tom Tobin wrote:
> On 5/9/06, gabor <[EMAIL PROTECTED]> wrote:
>> are there any scenarios when it's not a good idea to have [Slugs] as
>> primary keys? (except some hypothetical situations)
>
> The short answer: it's always a *bad* idea.
>
> The slightly longer answer: It's generally a bad idea
if i use a the admin fe i often would like to jump to the object of a
n:1 relation to edit that one. should not be that complicated or?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post t
On 5/9/06, gabor <[EMAIL PROTECTED]> wrote:
>
> are there any scenarios when it's not a good idea to have [Slugs] as
> primary keys? (except some hypothetical situations)
The short answer: it's always a *bad* idea.
The slightly longer answer: It's generally a bad idea to have your
primary key be
hi,
i'd like to know about your opinions regarding using Slugs as primary keys.
from how i understand them, if i use a Slug, then it makes usually sense
to have it as the primary key.
are there any scenarios when it's not a good idea to have them as
primary keys? (except some hypothetical situa
On 5/9/06, Kumar McMillan <[EMAIL PROTECTED]> wrote:
>
> this is all hypothetical since I haven't migrated any apps yet, but
> why would we want to have separate settings files if only the database
> config would change? To answer your question: I would ideally want to
> support these scenarios :
On Tuesday 09 May 2006 19:30, Kumar McMillan wrote:
>1. make a parse_dsn() function (since builtin urlparse doesn't
> handle user:pass splits) and carry it around with me on every django
> app I write. bah.
This seems like a good option to me, and I can't see too much wrong with
it. I ima
Cool! Very interesting to see a totally different kind of Django app.
I'll have to try it out.
On 5/8/06, ZebZiggle <[EMAIL PROTECTED]> wrote:
>
> Hey everyone!
>
> As you may or may not know (or are sick of hearing about) ... I've
> been dabbling on a web-game for a while now. It's called "My Da
this is all hypothetical since I haven't migrated any apps yet, but
why would we want to have separate settings files if only the database
config would change? To answer your question: I would ideally want to
support these scenarios :
1. developer running app on local machine
2. developer runnin
On 5/9/06, Kumar McMillan <[EMAIL PROTECTED]> wrote:
> Also, at my company we use sandboxed
> postgres (every user has his own database, named $USER) on our main
> dev server for better isolation. This means we pretty much have to set
> database settings as envionment variables.
Sorry, I'm not qu
How many Django'ers out there typically use DSNs for their web apps?
How are you currently working around Django's lack of DSN support?
I'm still new to Django, looking to migrate some existing apps to
Django plus start new ones, but without DSN support out of the box
it's almost a show stopper.
On 5/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Check to see in the changes if the lastest development version incluse
> support for supclassing models, I'm pretty sure I read somewhere that
> while it may appear to work on some levels the underlying code just
> isn't done or anywhere ne
Hey William,
Check to see in the changes if the lastest development version incluse
support for supclassing models, I'm pretty sure I read somewhere that
while it may appear to work on some levels the underlying code just
isn't done or anywhere near complete.
Good luck!
Andy.
--~--~-~
I ran into this problem as well. The issue is that super() expects the
child class not the parent class (the documentation is wrong), so try
this:
super(DahlBookManager, self).get_query_set()..
instead of
super(Manager, self).get_query_set()
In addition, it wouldn't let me create the Manage
Great, 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 [EMAIL PROTECTED]
On 5/9/06, tomass <[EMAIL PROTECTED]> wrote:
>
> The subject says it, really. Is there any way to access the
> request.user in the urls.py.
Nope, and there won't be due to decoupling and all. I'd recommend
creating your own view that just wraps the generic view. Something
like this:
from django.
Hi Folks,
The subject says it, really. Is there any way to access the
request.user in the urls.py. Basically I want to pass the current
user's id as an option to a generic view. I have a field in my model
which is a ForeignKey on User, so each instance of the model is
associated with a specific u
Hey folks,
now it all works here. And I really don't know where the problem was
:-((
sorry to bother you.
x0nix
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send e
I still haven't been able to confirm this particular display problem,
but adding the padding rule to #container doesn't break anything, so I
went ahead and commited that change.
On 4/29/06, parsch <[EMAIL PROTECTED]> wrote:
>
>
> Matthew Flanagan schrieb:
>
> > I can confirm that i'm seeing this
Okay point taken - I'll stop trying to be 'elegant' and just live with
the problem and deal with managing this with a 'VehicleType' model and
several redundant fields.
It is slightly anoying though!
--~--~-~--~~~---~--~~
You received this message because you are
On 5/3/06, tomass <[EMAIL PROTECTED]> wrote:
> I get no output/error messages when I try python automator.py.
>
> Here's the contents of the file:
>
>
> from django import template
>
> register = template.Library()
>
> @register.filter
> def bash_special(va
> Well, in *that* case: simply make a model based on this table. Or is
> there a problem I don't see?
I think he's looking for something a little more elegant, hence the
inheritance.
> Perhaps you want OneToOne as a simulation of constituent models? What
> is useful between different kinds of v
On 5/8/06, George Sakkis <[EMAIL PROTECTED]> wrote:
>
> I posted this in MySQLdb's tracker but it seems it has to do with
> Django. I have a view with one field being a time difference, computed
> as sec_to_time(unix_timestamp(end)-unix_timestamp(start)). MySQL
> specifies that the return type is
On 5/8/06, Paulo <[EMAIL PROTECTED]> wrote:
>
> Thanks for the tip! I will check it out when I get home this evening.
> I'll keep my fingers crossed that this will help me get django
> going... I've been wanting to start playing with Django for an
> upcoming project but am not a sys admin and can'
On 5/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Unfortunately this is not the case, I'm using the new version,
> downloaded through SVN.
No, you're not. Look at your stack trace - it references the 0.91 egg.
If you have downloaded the SVN version, it would appear that you
haven't cor
[EMAIL PROTECTED] wrote:
> I will say the way I'd be doing the inheritance more simply than is
> suggested on the wiki with one sparse table representing the whole
> inheritance hierarchy.
Well, in *that* case: simply make a model based on this table. Or is
there a problem I don't see?
Michael
On 5/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> As you can see inheritance would be very very useful for this purpose -
> so maybe I can work on that?
I'm not sure I see that. I know this is a canonical example of
inheritance, almost as popular as Shape and Square vs. Circle, but
those
I am building a website for a garage to put their cars etc. on. Said
garage also specialises in second hand vans and on occation trucks, I'd
like to know how I can represent the slightly different forms of data
using django, given that the inheritance is a work in progress and how
I can then disp
Unfortunately this is not the case, I'm using the new version,
downloaded through SVN.
--~--~-~--~~~---~--~~
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@googlegr
+1
On 5/9/06, Pradeep Kishore Gowda <[EMAIL PROTECTED]> wrote:
> +1 for HTTPS access.
--
Sincerely,
Vladimir "Farcaller" Pouzanov
http://www.hackndev.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django user
In the RemovingTheMagic wiki page the SQL to upgrade
django_content_type is given as:
UPDATE django_content_type SET name='group' WHERE model='group';
UPDATE django_content_type SET name='user' WHERE model='user';
The 'group' and 'user' should be plural. stuka fixes this to:
UPDATE d
So I decided the easiest way to do this was to add this to the top of
my model:
from django.contrib.auth.models import Group
and then adding this to my class:
group_perm = models.ManyToManyField(Group)
Thanks, Tom
--~--~-~--~~~---~--~~
You received this messag
43 matches
Mail list logo
