Hey all,
This week I implemented the metaclass based solution for backwards
compatibility in the Field API that Jacob suggested last week. Then I
implemented by first stab at a solution to the Oracle/backend with
custom query object problem. However, I don't have access to any of
the the DBs I'd need for that, so I'm appealing to django-developers.
If anyone has access to an Oracle DB (or any other backend with a
custom query object and doesn't mind doing the small bit of porting)
and wouldn't mind testing it out in an env with both Oracle and
another DB that would be most appreciated. All you'll need to do is
have a settings file with something like:
DATABASES = {
'default': {
'DATABASE_ENGINE': 'oracle'
etc...
}
'extra': {
'DATABASE_ENGINE': 'sqlite3',
}
}
And that should be enough.
For this week my goal is to get GeoDjango back into working order,
since I've broken it rather badly thus far.
Thanks,
Alex
--
"I disapprove of what you say, but I will defend to the death your
right to say it." -- Voltaire
"The people's good is the highest law." -- Cicero
"Code can always be simpler than you think, but never as simple as you
want" -- Me
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
