On Wednesday 07 December 2005 16:41, oggie rob wrote:
> Can somebody with checkin privs do this? I think the info I posted
> earlier will work (followed by a commit, of course):
> at top level of a clean checkout:
>
> svn propset snv:eol-style native -R .
s/snv/svn/
> cd contrib/admin/media/img/
Hi Pedro,
This is just a hunch - but you don't have PostgreSQL drivers for
Python installed do you?
If you're using mysql, just change "DATABASE_ENGINE" to mysql (or
whatever else you're using) and you should be able to run the server
(worked for me).
This is definetly a bug: Maybe it's better to
>This is just a hunch - but you don't have PostgreSQL drivers for
>Python installed do you?
>If you're using mysql, just change "DATABASE_ENGINE" to mysql (or
>whatever else you're using) and you should be able to run the server
>(worked for me).
I'll try to explain my point, Petar.
The auto-gen
I agree you shouldn't be forced to set up db, but that's not why you
had your problem - it was because you don't have postgresql driver for
python installed.
It tries do call them, fails and prints out an error. Switch it to
mysql (or whatever you're using) and everything will be honky-dory.
And I
> I agree you shouldn't be forced to set up db, but that's not why you
> had your problem - it was because you don't have postgresql driver for
> python installed.
> It tries do call them, fails and prints out an error. Switch it to
> mysql (or whatever you're using) and everything will be honky-d
How will 'or' queries work in the new get_list syntax?
-rob
Jacob Kaplan-Moss wrote:
* Model definitions (with properties, etc):
+1
* Database connections:
-0
* Putting lookups under Person.objects:
Not a fan of the aesthetic, but I can't think of anything better, and it
looks like it'll work fine, so...
+0
* Overwriting model methods
# Is there a reason we use a DoesNotExist rather than just
# using a single ObjectDoesNotExist exception for everything?
try:
p = polls.get_object(...)
c = choices.get_object(...)
except ObjectDoesNotExist, e:
...
Which one failed?
Having per-model DoesNotExist exceptions makes it p
On Dec 8, 2005, at 7:07 PM, Lachlan Cannon wrote:
Is there a reason we use a DoesNotExist rather than just
using a
single ObjectDoesNotExist exception for everything?
Yes.
Consider::
try:
do_something_that_involves_multiple_models()
except ModelOneDoesNotE
