On Sep 12, 11:14 am, Jason <[EMAIL PROTECTED]> wrote:
> yeah, that did work .. I'm just surprised I have to go through that
> extra step now, when
> before 1.0 release it seems I didn't have too :/
Great, but why would you think assigning a string to a Boolean field
would work in the first
yeah, that did work .. I'm just surprised I have to go through that
extra step now, when
before 1.0 release it seems I didn't have too :/
Anyways, thanks for the thoughts :)
On Sep 12, 6:15 am, Gremmie <[EMAIL PROTECTED]> wrote:
> On Sep 11, 11:55 pm, Jason <[EMAIL PROTECTED]> wrote:
>
>
>
> >
On Sep 11, 11:55 pm, Jason <[EMAIL PROTECTED]> wrote:
> I have a "true" or "false" string coming in from an ajax call to my
> view. I'm then turning around and directly assigning that string from
> the front end to my model object and saving it.
>
> Before the upgrade to django 1.0, the database
I have a "true" or "false" string coming in from an ajax call to my
view. I'm then turning around and directly assigning that string from
the front end to my model object and saving it.
Before the upgrade to django 1.0, the database happily accepted my
model object's value as 'true' or 'false'
4 matches
Mail list logo
