Michael Richardson wrote: > Why does trac/db/postgres_backend.py reset the search_path if you > tell it to use a schema? I can see why this might be desired by some.
Because I'm lazy? Now, for the other question, why might it be desirable for some? The main thing that schema support requires is that the schema is first in the search_path. Your patch looks good. However, perhaps the better way is to preserve the entire search path. While I'm sure most everyone will only have the trac schema and public in their search_path, I it's feasible that something more could be in it. -John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
