Thanks, Tom. (This is Matt, following up on the dev list.) The issues we're seeing with your latest Oracle patch on top of Django 0.95 do mostly pertain to a syncdb. Specifically, it looks as though Oracle's 30-character limit on most identifiers is not taken into account, so some constraint definitions fail. This is a shame, since Django appears to emit a good schema with integrity otherwise.
The other problem (which I provided a hacked-up "solution" for in a comment on bug #1990) is that Oracle barfs on the optional AS keyword in some cases. Omitting "AS" fixes this, but requires another "if settings.DATABASE == 'oracle'" clause, which I'm guessing gets us no closer to being included in the source tree. Another problem we're seeing once up and running is some queries have two named args, both named ":arg" in the SQL, which causes the first bind parameter to be used twice. Anyway, I'll try to document these problems more cleanly. We would like to get into helping with this. I'll keep watching this list and keep communicating--we can all get it done together. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
