Not sure which thread this is the tail of, but it seems obvious to me
that you haven't set the DATABASE_ENGINE. Try eding your settings.py
and changing the line to:
DATABASE_ENGINE = sqllite3
Sorry if I haven't understood your problem correctly.
Cheers
Greg.
On Apr 29, 9:41 am, fedex1
Hi Greg and Everyone,
Do you happen to know where the documentation on this is.
The odd thing is the code works fine with the DATABASE_ENGINE set to
'' 99% of the time.
It's only a few times that it fails.
I suspect it's a write failure and I simply have to perform a retest,
but I don't see
Hi Howard,
We need much more information to be of any assistance. Where are you
getting this error? Using Java, or Python?
Please post the complete stacktrace, as well as any relevant code and
configuration files.
-Nick Johnson
On Wed, May 6, 2009 at 4:01 AM, Howard hhs...@gmail.com wrote:
I am getting the exact the same error, under python runtime
when I check the log , I got pages of such errors, I know nothing
about this ,
seeming that if I set DEBUG = TRUE will decrease such errors but I am
not sure of this
stack trace:
class 'django.core.exceptions.ImproperlyConfigured': You
It is a very weird error, you know , It just don't happen all the
time, but if I trigger /service/bbs/ (a django gateway for PYAMF) and
the service is not completed, I got my whole site down and all errors
were about DATABASE_ENGINE setting etc, and after a while it recovers
automatically
If you
just for the record, DATABASE_ENGINE is a django thing, not an app
engine thing.
(that's as much as i can help, since i don't really know anything
about django.)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
