Sorry for disappearing there.
I didn't think a full trace was necessary, russ nailed that particular
instance. As a user of django, I don't think for 1.5 that you need to
change the behavior of views. It just blind sided me that the custom auth
model needed an integer ID and it should be added
That pattern has nasty side-effects. It can be used in some cases but it
fails in most.
On Friday, November 9, 2012 8:28:47 AM UTC-7, Daniel Sokolowski wrote:
>
> I’ve done the below in the past, the only issue with that is if you
> have side effects in parent’s dispatch you don’t want
Hi,
Has anyone run into an issue where dumpdata refers to the old auth model
and tries to dump its data?
Here is what I am encountering:
DEBUG 2012-11-09 11:49:46,363 util 8457 140488053692160 (0.002) SELECT
"auth_user"."id", "auth_user"."password", "auth_user"."last_login",
I’ve done the below in the past, the only issue with that is if you have side
effects in parent’s dispatch you don’t want executed but you would also run
that risk if you had an initialize() method work flow; in the end I find
dispatch() is enough in my experience.
def dispatch(self, request,
When I was working on a similar issue for django-selectable I created an
issue to address this problem with a simple proof of concept patch
https://code.djangoproject.com/ticket/15760. However I never followed
through with the ticket to try to get something like this added. In the
meantime
On Friday, 9 November 2012 00:31:39 UTC+1, Russell Keith-Magee wrote:
> If you can show a clear difference in behaviour between 1.3 and 1.4, then
> you've definitely found a bug. If you can log this in Trac (and mark it as
> a release blocker, since it's a change in behaviour), we can
Hi all,
Is it possible to trigger an event on add-another ?
Or is there a better solution to work around this problem ?
https://github.com/yourlabs/django-autocomplete-light/blob/master/autocomplete_light/static/autocomplete_light/widget.js#L267
Thanks for answering
Regards
--
You received
