Adrian> No can do -- that would couple the database layer to HTTP,
which
Adrian> wouldn't be a good thing.
James> I wonder, though, if this is a case of practicality beating
purity;
James> also, it's incredibly ugly to raise an exception that says "I
couldn't
James> find what you asked for" and
Or, maybe, a better solution would be to keep the distinction (since
it is useful for debugging) but rename it.
The core problem, I think, is that Django is primarily used for web
applications, which means that everything revolves around HTTP
request/response cycles. And in that context, "does n
On 1/5/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
No can do -- that would couple the database layer to HTTP, which
wouldn't be a good thing.
I wonder, though, if this is a case of practicality beating purity;
also, it's incredibly ugly to raise an exception that says "I couldn't
find what
