ver ordering occurs on
> null=True relationships on any of the major field types.
>
> gav
>
> On Jun 23, 2008, at 10:00 AM, Mike H wrote:
>
>>
>>
>> Gah... ignore! Even though the foreignkey was nullable, I had an
>> ordering entry in the Meta class which orde
Gah... ignore! Even though the foreignkey was nullable, I had an
ordering entry in the Meta class which ordered by deployment__name
which forced the inner join.
I'll be quiet now... ;-)
Mike
On 23 Jun 2008, at 14:51, Mike H wrote:
>
> Hi all,
>
> Before I rush off and possibly
Hi all,
Before I rush off and possibly file a bogus bug report, am I seeing
incorrect behavior here?
I have a simple 'Project' model, as so:
class Project(models.Model):
deployment = models.ForeignKey(Deployment, blank=True, null=True)
... some other fields here
Some of the
Solved : adding editable=False to the total field stops this
behaviour, so it was something I was doing wrong ;) Although I didn't
expect the posted data to override the data I set in save() ...
Cheers,
Mike
On Feb 5, 3:01 pm, MikeH <[EMAIL PROTECTED]> wrote:
> However, when I do the
Malcolm Tredinnick wrote:
> Don't reopen issues that have been marked "wontfix". This mark
> means that the decision has been made that we can't or won't fix
> this particular issue. If you're not sure why, please ask on
> `django-developers`_.
>
> That's
Derek Anderson wrote:
> i have had this exact situation happen to me before. (rolling out a
> change, then another change reversing it) actually several times. i
> have NEVER had a scenario where client Y says "can you please make sure
> i lose my data?"
>
>
That doesn't mean that other
Russell Keith-Magee wrote:
> 3) If you are using fingerprints to identify nodes in the graph, how
> do you handle cyclic states (e.g., v1, I add a field, v2 delete it ,v3
> add it again)? As I read your proposal, the fingerprint for v1 and v3
> should be the same - which will cause some major
Hi,
> 6) The user can define evolutions. They exact sequence is defined in
> the Meta property of the model:
>
> class Author(Model):
>...
>class Meta:
> evolution = [
> 'v1',
> 'v2',
> 'pre_christmas_2006',
> 'valentines_day_2007',
>
Sorry, I'll file a ticket in trac in future, and I had no idea google
groups would file the email as it did, I thought I was starting a new
discussion.
I'll keep it in mind in future :)
Mike
Malcolm Tredinnick wrote:
> On Sun, 2007-06-17 at 20:08 +0100, Mike H wrote:
>
>> Hi
Thanks, didn't occur to me to use that :) Perhaps the example in the
docs needs updating to show required=False in the cc_myself field? Would
make a bit more sense as that form actually forces you to cc yourself ;)
Cheers,
Mike
SmileyChris wrote:
> On Jun 18, 8:44 am, Mike H <
Hi all,
Perhaps I'm not using it correctly, but I'm not able to use the
BooleanField in newforms in the way the documentation suggests I should
be able to.
Here's the example :
class ContactForm(forms.Form):
subject = forms.CharField(max_length=100)
message = forms.CharField()
Whoops, just saw I had "possessive" spelled incorrectly... revised the
patch!
Cheers,
MikeH
--- django0.96/template/defaultfilters.py 2007-03-10
08:11:28.0 +
+++ django/template/defaultfilters.py 2007-06-17 20:02:50.0 +0100
@@ -551,6 +551,15 @@
pass
Hi all,
I needed a nice way of saying "mike's friends" in a template when the
currently logged in user was "mike", but "james' friends" when it was
james. I realise this is a very English biased filter, but here's a
patch to add it to defaultfilters in template.
Cheers,
MikeH
---
I'd like to see alternative session backends so that I can write one
that uses memcached (which I use as standard on any high traffic PHP
sites I write).
Cheers,
Mike
buriy wrote:
>>> However, that's a good reason to have sessions pluggable -- if
>>> persistence is important, then you need
14 matches
Mail list logo
