Malcolm Tredinnick wrote:

> Yeah, you're right. I've been sucking a lot on this and keeping others
> back. Everybody's been very restrained and understanding.
>
> I need to stop changing my mind about what to do and stop getting
> distracted by shiny objects like other bugs and finish this, or at least
> get to the point that everybody can pitch in.
>
> So, here's the plan: I'm going to go quiet on fixing other bugs and
> possibly replying to non-essential Django e-mail for the rest of this
> week and finish the code. I'm between jobs at the moment, so I can
> devote time to it.

while your at it, i'm struggling with query stuff for a while now for
a
relative special model/field.

code:

https://dev.leipzig.freifunk.net/trac/browser/ffsomething/branches/generic/apps/management/models.py


What we need is a real IP Field, that can contain ip adresses (both
IPv4
and IPv6) as well as whole networks and does right ordering.
128 bit integer values are not available everywhere, so i decided to
split it into 4 32 bit integers.

As much as I read through the code, implementing this as a field is
not
supported, so I used a Model. However, implementing the model smoothly
isn't done easily. Currently is stuck transforming filter arguments:

>>> NetworkAddress.objects.filter(ip="192.168.1.1/32")
[<NetworkAddress: 192.168.1.1/32>]

however, ip does not exist and should be a simple to use alias for a
complex internal structure.

The problem is, that there is no hook or callback function in
parse_lookup and the only way I see currently is by tranforming every
Q
object in _filters.

But I'm absolutly unsure if I'm on the right track :)

kindly regards
 daniel


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to