Hello,
#19468 sparked an interesting debate; Claude and I would like some feedback
before making a decision.
Here's a summary of the problem.
Django must decode environ['PATH_INFO'] to obtain request.path, where
decoding means :
1 - URL-decoding to a bytestring
2 - "charset-decoding" to an unico
Héllo,
Sorry to shim in a probably a bit off and old topic discussion, I think we
need to have this discussion, even if this is similar to any other nosql
discussion, there is nothing really specific to OrientDB or any graphdb
(Neo4J, Rexster server, ...).
I have no particular experience with
On Mon, Dec 17, 2012 at 3:40 PM, maxi wrote:
> I was seeing that the new URLField [1] is just defined on oracle backend
> (into creation.py)
> Why not in other backend modules?
Actually, I think that line in oracle/creation.py is dead code. The
internal type of URLField is CharField, so the Char
I was seeing that the new URLField [1] is just defined on oracle backend
(into creation.py)
Why not in other backend modules?
Best Regards.
---
Maximiliano Robaina
django-firebird backend maintainer.
[1] https://docs.djangoproject.com/en/dev/ref/models/fields/#urlfield
--
You received this me