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'
Hey all,
This week I made the final major API changes, updating the
get_db_prep_* methods to recieve connection, and work in a backwards
compatible method. I also fixed the bug with using
__in=queryset.using('other_db'), right now it raises an exception, but
in the future I'll update it to just
Hey all,
This past week unfortunately wasn't super eventful. I did some final dead
code elimination on my m2m-refactor branch, I was able to kill about 150
additional lines of code that no longer needed, there are a few small
changes I need to make to remove some quadratic behavior that occurs du
Hey all,
Sorry about the delayed update, wanted to touch base with my mentor on a few
small issues before firing this off. I spent last week augmenting
ManyToManyFields to use a full Model internally, so we can remove some hard
coded SQL. I've been doing this on a separate branch since it's a fa
I would agree with you on the dict issue, given that some of the
backends have custom settings etc. I also agree that this is not
really something that matters now - DSNs will need to be parsed into
dicts anyway, so you might as well implement the dicts first and then
see what the demand is for DS
Hi all,
Not a lot of new news or progress. I'll be at EuroDjangoCon all of next
week so I may be starting my work there, depending on the status of 1.1.
The only new news was Simon and I discussed switching to a DSN string in
place of the dict of settings. Personally I'm -1 on that as I find the
