Please take this conversation elsewhere as per my previous post.
On Wed, 11 Aug 2021 at 13:33, Umar Farooq
wrote:
> Sorry code screenshots
>
> On Wed, 11 Aug 2021, 5:27 PM Rana Zain, wrote:
>
>> Okay I am sending screenshot.[image: erroits.PNG]
>>
>> On Tuesday, August 10, 2021 at 6:26:42 PM UT
As Adam has stated, this is not a forum to discuss issues with your code.
Please see the links in his reply.
Kye
> On 11 Aug 2021, at 8:35 pm, Umar Farooq wrote:
>
>
> Sorry code screenshots
>
>> On Wed, 11 Aug 2021, 5:27 PM Rana Zain, wrote:
>> Okay I am sending screenshot.
>>
>>
>>
>
Sorry code screenshots
On Wed, 11 Aug 2021, 5:27 PM Rana Zain, wrote:
> Okay I am sending screenshot.[image: erroits.PNG]
>
> On Tuesday, August 10, 2021 at 6:26:42 PM UTC+5 Adam Johnson wrote:
>
>> Hi!
>>
>> I think you've found the wrong mailing list for this post. This mailing
>> list is for
Okay I am sending screenshot.[image: erroits.PNG]
On Tuesday, August 10, 2021 at 6:26:42 PM UTC+5 Adam Johnson wrote:
> Hi!
>
> I think you've found the wrong mailing list for this post. This mailing
> list is for discussing the development of Django itself, not for support
> using Django. This
Hi!
I think you've found the wrong mailing list for this post. This mailing
list is for discussing the development of Django itself, not for support
using Django. This means the discussions of bugs and features in Django
itself, rather than in your code using it. People on this list are unlikely
t
Can you send the screenshot
On Tue, 10 Aug 2021, 6:19 PM Rana Zain, wrote:
> I am facing this errors :
>
> > ',' or ')' expected
> > Unexpected indent
> > Statement expected, found Py:DEDENT
>
> for the last 2,3 days. Kindly help me out.
>
> --
> You received this message because you are subscri
On Apr 11, 2:50 pm, Łukasz Rekucki wrote:
> As for the error, it's quite a puzzle. If update() tries to iterate
> thru value, it means it's a non-empty sequence that's not a subclass
> of dict, right? Did you manage to track what type of value it is?
> There must be a bug somewhere else too.
Whe
On 11 April 2012 13:37, Vinay Sajip wrote:
> The errors seem to be related to Aymeric's change in r17894. If I
> change
>
> def _reset_dicts(self, value=None):
> builtins = {'True': True, 'False': False, 'None': None}
> if value:
> builtins.update(value)
> self.d
The errors seem to be related to Aymeric's change in r17894. If I
change
def _reset_dicts(self, value=None):
builtins = {'True': True, 'False': False, 'None': None}
if value:
builtins.update(value)
self.dicts = [builtins]
to the seemingly equivalent
de
The lack of boolean type coercion is more serious than it looks like at
first glance.
(starting from the example at http://code.djangoproject.com/ticket/7190)
In [1]: import django.newforms as forms
In [2]: from django.newforms.models import model_to_dict
In [3]: from simple.models import Simple
On Jun 19, 3:04 pm, Steve Holden <[EMAIL PROTECTED]> wrote:
> Well I guess the obvious (time consuming, painful) way would be to
> validate the semantic integrity from Django in the back end. That could,
> if automated, get horrendously time-consuming for even quite small
> changes to the databas
Your patch works, thanks. Perhaps you could add it to
http://code.djangoproject.com/ticket/7190; I tried the patch there, but
it doesn't work in this case.
Mike
Pim Van Heuven wrote:
> Hi Michael,
>
> Can you apply this patch and run the tests again?
> I have been running Django with this pa
Hi Michael,
Can you apply this patch and run the tests again?
I have been running Django with this patch for a long time but never
got around to submitting it.
Pim.
Michael Glassford wrote:
> I'm still trying to run the Django unit tests for the first time. I've
> worked through most of the e
On Thu, Jun 19, 2008 at 9:57 AM, Michael Glassford <[EMAIL PROTECTED]>
wrote:
>
> I'm still trying to run the Django unit tests for the first time. I've
> worked through most of the errors--all of them so far proved to be
> caused by the MySQL/InnoDB ordering problem when deserializing objects
> t
Russell Keith-Magee wrote:
> On Thu, Jun 19, 2008 at 9:04 PM, Peter Melvyn <[EMAIL PROTECTED]> wrote:
>
>> On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>>
>>
>>> (2) provide a way to manually disable and re-enable integrity checks. If
>>> someone with more MySQL-fu than me
On Thu, Jun 19, 2008 at 9:21 AM, Russell Keith-Magee <[EMAIL PROTECTED]>
wrote:
>
> On Thu, Jun 19, 2008 at 9:04 PM, Peter Melvyn <[EMAIL PROTECTED]>
> wrote:
> >
> > On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> >
> >> (2) provide a way to manually disable and re-enable integrity
On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> However, I was under the impression that this has the effect of
> disabling, not just deferring key checks - that is, if you disable
> checks, load bad data, then re-enable checks, no errors will be
> raised. We don't want to be res
On Thu, Jun 19, 2008 at 9:23 PM, Michael Glassford <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
>> Yes, it is. Unfortunately, the best way to fix this is for MySQL to
>> either (1) implement transaction level key integrity checks, or (2)
>> provide a way to manually disable and re-ena
Russell Keith-Magee wrote:
> On Thu, Jun 19, 2008 at 3:44 AM, Michael Glassford <[EMAIL PROTECTED]> wrote:
>
>>> from what that says I'd guess you are using the InnoDB MySQL storage
>>> backend,
>> Right you are. That limitation is a bit of a pain.
>
> Yes, it is. Unfortunately, the best way to
On Thu, Jun 19, 2008 at 9:04 PM, Peter Melvyn <[EMAIL PROTECTED]> wrote:
>
> On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>> (2) provide a way to manually disable and re-enable integrity checks. If
>> someone with more MySQL-fu than me knows how to do either of these
>
> It shoul
On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> (2) provide a way to manually disable and re-enable integrity checks. If
> someone with more MySQL-fu than me knows how to do either of these
It should work:
SET FOREIGN_KEY_CHECKS = 0;
... imported data ...
mysql> SET FOREIGN_KEY
On Thu, Jun 19, 2008 at 3:44 AM, Michael Glassford <[EMAIL PROTECTED]> wrote:
>> from what that says I'd guess you are using the InnoDB MySQL storage backend,
>
> Right you are. That limitation is a bit of a pain.
Yes, it is. Unfortunately, the best way to fix this is for MySQL to
either (1) imp
Ramiro Morales wrote:
> On Wed, Jun 18, 2008 at 3:51 PM, Michael Glassford <[EMAIL PROTECTED]> wrote:
>> I'm trying to run the Django unit tests for the first time using
>> runtests.py and I'm getting a lot of errors like this:
[snip]
> This could be related to the "MySQL and Fixtures" note cont
On Wed, Jun 18, 2008 at 3:51 PM, Michael Glassford <[EMAIL PROTECTED]> wrote:
>
> I'm trying to run the Django unit tests for the first time using
> runtests.py and I'm getting a lot of errors like this:
>
> [...]
> "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/MyS
Hey Adrian,
Adrian Holovaty wrote:
> Michael, you have stumbled upon an idea that I've coincidentally also
> wanted to do since before Django was open-sourced! See
Very Nice ;-)
But have you checked how I'm doing this different?
- Since data that does not pass tese "advisory tests" can get into
On 6/7/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Now, is there interest in having such a thing in Django? Currently, I try to
> keep the
> patching minimal, but I don't see how I could avoid it. If this would go into
> Django
> eventually, it could be solved cleaner and easier. For exampl
26 matches
Mail list logo
