On Mon, Jan 24, 2011 at 3:26 PM, Rahul wrote:
> Hi,
>
> I am working on upgrading DB2 Django adaptor for 1.3. I had a small
> question on the above. As per the docs of 'DO_NOTHING', you mention
> 'IF' your DB backend enforces referential integrity, this will cause
> an IntegrityError.
> http://do
Hi,
I am working on upgrading DB2 Django adaptor for 1.3. I had a small
question on the above. As per the docs of 'DO_NOTHING', you mention
'IF' your DB backend enforces referential integrity, this will cause
an IntegrityError.
http://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.mo
Hi,
I am stuck while look into source code of Django's lazy decorator. At
line 205 of functinal.py, there is:
def __unicode_cast(self):
return self.__func(*self.__args, **self.__kw)
def __str_cast(self):
return str(self.__func(*self.__args, **self.__kw))
Why doesn't __unic
Hi,
#2594 is now ready for checkin as far as I can tell for the 1.4 milestone (I
understand 1.3 is closed), with one side-issue.
http://code.djangoproject.com/ticket/2594
The side issue is that msgids in the .po file extracted with makemessages
will not match the untranslated string that Djang
Thanks for the detailed explanation Russ. I was mainly concerned about
jumping into to attempt to rework a few things without a better
understanding of what the code is supposed to be doing.
If I find a few minutes today, I was thinking about writing a few
tests specifically against the __init__ m
Greetings All,
In the firebird backend for django, it has been noticed that if a
legacy DB model contains a COMPUTED BY field, INSERTs and UPDATEs will
fail on that model - because firebird itself rejects any attempt to
update that field.
(for example, a field is defined in DDL as: FULL_NAME COMP
On Mon, Jan 17, 2011 at 1:16 AM, Vincent wrote:
> When looking through the test client I noticed that it requires a
> dictionary and always uses multipart/form-data posts. Sometimes it's
> helpful to use a raw post, instead. The flexibility allows you to just
> post a string, use key-value pair fo
On Fri, Jan 21, 2011 at 5:50 AM, Alexey Toptygin
wrote:
> I've been reading django/db/models/fields/files.py to figure out how
> FileFields work under the hood, and I've noticed a bit I don't
> understand. The __getstate__ method of FieldFile does:
>
> return {'name': self.name, 'closed': False, '
On Sat, Jan 22, 2011 at 2:27 PM, Jim D. wrote:
> Howdy,
>
> I reported a bug earlier today (http://code.djangoproject.com/ticket/
> 15144) related to a possible regression in changeset 15021 (http://
> code.djangoproject.com/changeset/15021). The apparent regression is
> that as of this changeset,
