On 7 nov. 2013, at 16:39, Vajrasky Kok wrote:
> So I already created a pull request to modify this document. But there was a
> gentleman who raised objection that the ability to override site header was
> really not that important and was better skipped in
Greetings, friends!
I found a bug (https://code.djangoproject.com/ticket/21378) in tutorial02
(dev/1.7 version) which can be found here:
https://docs.djangoproject.com/en/dev/intro/tutorial02/. To change site
header, I was told to override the "generic Django text" in the template.
But in
On Thu, Nov 7, 2013 at 10:59 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> But if you're using a ModelForm — like the admin does — then you need some
> code to convert empty strings to None. I believe that's the problem
> Vlastimil wants to solve.
>
Got it.
Thanks for the
2013/11/7 Elyézer Rezende
> Setting null=True in the field definition and doing model.field = None
> doesn't do this?
>
At the model layer, yes.
But if you're using a ModelForm — like the admin does — then you need some
code to convert empty strings to None. I believe
Setting null=True in the field definition and doing model.field = None
doesn't do this?
If you create a gist or a paste with a sample code would help understand
better.
On Thu, Nov 7, 2013 at 8:37 AM, Vlastimil Zíma wrote:
> Hi everybody,
>
> I know this was here before,
On Thu, Nov 7, 2013 at 5:37 AM, Vlastimil Zíma wrote:
> I don't want to enforce anybody to use only NULL as empty value, I just
> want Django to store NULL in database when I told it to. And I don't mean
> the way of overriding all the form fields as I have to now.
>
A
Hi everybody,
I know this was here before, but it is really a problem. We need (I
literally mean need, not just want) a simple way to store NULL in database
instead of ''. Using empty string has several serious consequences (in
databases which distinguishes between NULL and '', which are to my
LGTM
On Thu, Nov 7, 2013 at 8:40 AM, Elyézer Rezende wrote:
> +1
>
> This gives an overview that what behaviours users could find when dealing
> with some use cases of the ORM.
>
>
>
> On Wed, Nov 6, 2013 at 6:14 PM, Anssi Kääriäinen
> wrote:
>>
>>
+1
This gives an overview that what behaviours users could find when dealing
with some use cases of the ORM.
On Wed, Nov 6, 2013 at 6:14 PM, Anssi Kääriäinen wrote:
>
>
> On Tuesday, November 5, 2013 1:02:41 PM UTC+2, Anssi Kääriäinen wrote:
>>
>> Adding something