Russell Keith-Magee wrote:
> On 8/21/07, George Vilches <[EMAIL PROTECTED]> wrote:
>> All,
>>
>> I've looked everywhere in the Django unit tests and can't find anywhere
>> that's testing these four signals:
> ...
>> Thoughts?
>
> Only one thought - put this in a ticket so it doesn't get lost or
On 8/21/07, George Vilches <[EMAIL PROTECTED]> wrote:
>
> All,
>
> I've looked everywhere in the Django unit tests and can't find anywhere
> that's testing these four signals:
...
> Thoughts?
Only one thought - put this in a ticket so it doesn't get lost or forgotten.
Yours,
Russ Magee %-)
On Aug 22, 4:12 am, "Rob Hudson" <[EMAIL PROTECTED]> wrote:
> ...then importing a model from application.models.modelA or whatever
> doesn't work out of the box. So, you have to manually set the
> Meta.app_label attribute on each model so that it knows how to work out
> which app it belongs to.
Aha - it seems to work, at least for simple cases, if I'm using MySQL
and not sqlite.
Sorry to bother you!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
OK, I realise I've got a slightly unusual case here and don't want to
take much of anyone's time, but I wondered if it would be easy to make
it work...
I wanted to do a simple test which involved the database being queried
and updated from two different threads. (In real life this is to do
with
Hi Devs,
I'm working on a patch for #5177
(http://code.djangoproject.com/ticket/5177) which will clean up
orphaned content types and Malcolm questioned, "What happens if a
model has Meta.app_label set?" and further went on to explain that it
was never clearly determined if app_label should only
I'm interested in the status too, and I'm willing to help out w/any
implementation. I've got a few feature requests for this refactor;
specifically, the possibility of mainlining several of the
modifications I've made in the GIS branch that assist in constructing
spatial SQL.
-Justin
All,
I've looked everywhere in the Django unit tests and can't find anywhere
that's testing these four signals:
pre_save
post_save
pre_delete
post_delete
I found the dispatcher tests, which cover all the generic bits, but
nothing specifically for these model signals.
On the assumption that
On Aug 21, 3:54 pm, pk11 <[EMAIL PROTECTED]> wrote:
> As far as I see we could
>
> 1) add a simple method like this to the db
> api:http://code.djangoproject.com/ticket/5101
There are two ways you could implement validation...one at the
database level and the other at the application level. My
On Mon, 2007-08-20 at 23:33 -0500, Adrian Holovaty wrote:
> Malcolm -- what's the status of the query.py refactoring you've been
> working on? We have a bunch of features waiting for that refactoring,
> including SQL aggregation support.
>
> It'd be great to land that refactoring once and for
Am 21.08.2007 um 04:54 schrieb Marty Alchin:
> On 8/20/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>> There is indeed a reason: model field validation logic is in a
>> separate module so that the logic doesn't have to be loaded into
>> memory when you're using Django in production. As it
On 8/20/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> There is indeed a reason: model field validation logic is in a
> separate module so that the logic doesn't have to be loaded into
> memory when you're using Django in production. As it stands, the
> validation code is only loaded when you
On Tue, 2007-08-21 at 03:54 -0700, pk11 wrote:
> hi all,
>
> a while back(http://groups.google.com/group/django-developers/
> browse_thread/thread/fef854223b97e49c/c0e0ccce78369f05?
> lnk=gst=validation+aware+models=4#c0e0ccce78369f05) there was a
> discussion about adding a way to perform
hi all,
a while back(http://groups.google.com/group/django-developers/
browse_thread/thread/fef854223b97e49c/c0e0ccce78369f05?
lnk=gst=validation+aware+models=4#c0e0ccce78369f05) there was a
discussion about adding a way to perform validation before saving an
object.
As far as I see we could
hi all,
a while back(http://groups.google.com/group/django-developers/
browse_thread/thread/fef854223b97e49c/c0e0ccce78369f05?
lnk=gst=validation+aware+models=4#c0e0ccce78369f05) there was a
discussion about adding a way to perform validation before saving an
object.
As far as I see we could
15 matches
Mail list logo
