Absolutely right, I have been working on it all evening too. I think I know what the problem is but I need to ask in dev anyway just to figure out the best way to go about it.
On Oct 25, 8:13 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2007-10-25 at 15:31 -0700, Zenom wrote: > > OK so I am working on ticket # 1051 which is the PostgreSQL > > search_path ticket. I checked out trunk today and made a diff. When I > > go to the shell and create queries and save data it works like a > > champ. When I try to run a test it gives me a > > psycopg2.ProgrammingError saying that the schema doesn't exist. > > > What is confusing is that it errors out saying the 'andy' schema > > doesn't exist, so it obviously knows what the schema name is. It's the > > same one that works when I try to do normal queries. > > > Is there something else anyone can think of that I might need to > > change for tests to work? This wont get submitted without a test and > > well i can't submit if I cannot test. > > So you are saying that in an unknown collection of code changes that we > haven't seen, you are getting a very specific error message and you are > wondering if we can help debug it? Does it strike you that there might > be some information missing there for anybody to be able to help? :-) > > > On a side note, what kind of tests should I perform to help make sure > > this gets accepted into Django. This is a very important piece for our > > company and would like to see it as part of the base install. > > Well, for a start, you should have any design discussion on django-dev, > instead of django-users. That's where development work takes place and > we try very hard to keep the two domains separate. > > I think there's still some design work needed. For example, there's a > comment (#13) declaring that certain things were in and out of scope for > the ticket. However, I'm not sure that's a done deal, since it hasn't > been discussed anywhere. For example, work out how this might work > API-wise and then discuss it on django-dev to see if the same syntax > will work smoothly with, e.g., Oracle. You don't have to do the backend > work for Oracle, but having a public API that works well for the two > main systems that support schemas is really going to be a requirement > here. > > So come up with an API, maybe even come up with a code patch -- > particularly since you already have one, it seems -- and then start a > thread on django-dev to solicit opinions. My gut feeling is that it > won't be too controversial, but we should get the API "right", for th > reasons indicated above. > > Regards, > Malcolm > > -- > On the other hand, you have different > fingers.http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
