where the hook can be used
to implemented custom behaviour (so that at least we have only 1 function
to create users). Would this be a better design? Or is the current
design the correct one, and am I missing something? (in that case, please
elaborate)
Best regards,
Maarten
--
You received
I would use geography. You never know from where the user is coming, so you
don't know the limitations of the projection. If you need extra
functionality you can always transform to the most appropriate projection.
2012/10/21 JJ Zolper
> Hello,
>
> So I've been researching the pros and cons fo
Great! this works. Thank you so much Kevin.
2012/3/18 Kevin Wetzels
>
> On Sunday, March 18, 2012 12:55:31 PM UTC+1, Maarten Japink wrote:
>>
>> I 'm working on a taxonomie.
>> These are my models:
>>
>> class Classificatie(models.Model):
>
I 'm working on a taxonomie.
These are my models:
class Classificatie(models.Model):
name=models.CharField(max_length=60)
def __unicode__(self):
return self.name
class Taxonomie(models.Model):
name=models.CharField(max_length=60)
level=models.ForeignKey(Classificatie)
Shouldn't it be pointed out in the tutorial that if you use a non-root
path for your django-installation, the hard-coded form-action won't
work?
On Feb 10, 2:27 pm, "a...@amos-site.org.uk"
wrote:
> Where exactly do you put this I'm guessing in the file, but a bit of
> context would be appreciate
Hey,
I'd like to help out. But there is limited information to go on.
Those options, are that all seperate attributes of your object, or is
it one more general 'description' attribute with those different
options.
How do you want to filter it, when and what exactly?
I'm thinking you want to app
Just on another note,
it doesn't seem that smart to me to use a CharField(max_length=600)
for a primary key.
I'd use the normal id as primary key, and if you need to use the url
actively in searches I'd consider adding an index on the url field.
cheers,
Maarten
On Jan 15, 4
Hi,
I'm notan expert with django yet, but I do recommend to keep your
models and not throw everything into 1 big model. The relations are
powerfull, don't throw it out even if it means having to write a nest
or two.
Let's use the following model to look into this:
Models: A, B and C. C is a pa
Hello
"""
def songs(request):
songs_listing = []
for songs_list in Song.objects.all():
songs_dict = {}
songs_dict['list_object'] = songs_list
songs_listing.append(songs_dict)
return render_to_response('songs/songs.html',
{ 's
esponseredirect
else:
rendertoresponse(... { 'error_list':getErrors,
'message_list':getMessages})
cheers,
Maarten
On Jan 3, 7:38 pm, Peter Rowell <[EMAIL PROTECTED]> wrote:
> I didn't like my own explanation and did a little more searching.
>
> I just
Ah, just to be clear:
the request.POST.has_key('name') searches for the name of the tag and
value is what you get when doing
you_get = request.POST['name']
On Jan 4, 10:14 am, Maarten <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a view with that also requires
ency a bit), it's not as clean though.
try:
request.POST['whatever_field_you_need'] ...
except KeyError, e:
try:
request.POST['the_second_fields_you need]
except KeyError, e:
etc...
Ok, now that I've written this bit down I'm actually going to change
this last thing
"...",
category = request.POST['id'])
Don't know if this is exactly what you are asking, but it should help
out.
Regards,
Maarten
hern42 schreef:
> Hello,
> I have an issue (it might be a beginner issue, if so I am sorry...
> please point to the chapter in the doc)
quot;wrong syntax in entry: %s"%line)
return HttpResponseRedirect('/stock/new/')
else:
errors.append("Please specify a PO")
return render_to_response('stock/stock_new.html',
{'error_list':errors, 'po_list':PO.objec
14 matches
Mail list logo
