-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "John" == John Hampton <[EMAIL PROTECTED]> writes:
>> 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.
John> Because I'm lazy? Now, for the other question, why might it
But, you did more work. If you didn't tough the search_path, it would
have stayed at $USER,public :-)
John> be desirable for some? The main thing that schema support
John> requires is that the schema is first in the search_path.
True.
I think, some people might not want public in their search path, if
the point of using schemas was to seperate trac from some other set of
tables, needed by some plugin. However, if they have overlapping table
names, but all of the tables exist in trac's schema, then I am not sure
that it matters.
Are there any optional tables in trac? I don't think so...
- --
[EMAIL PROTECTED] / [EMAIL PROTECTED]
XDS Inc, Ottawa, ON
Personal: http://www.sandelman.ca/mcr/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Finger me for keys
iQEVAwUBRrsQLoCLcPvd0N1lAQKD0AgAtEf3iNkjN5OOlqaM6qK4Od1ono+GnsAk
VRxu/5k0fbubQRKgJrMNJmbPOxVVyoC/Pq91XwUkec4LpLG5g1Jx8lEj2vkuKXO5
36m8f6P5eacLSwM6enE1inSzl9WPhziMznLwiTpCxSZC1WLXMI4pP//QtBKIfnSc
EuxMrAK6Qb5IDmIpJ5eApQfnroL4q/WOS5ewR7NQAHNrReKBrfYIXfSyPzugFd3w
wLq8zm6NvIyani/dDxRC/H3hPm4jjtTWaADOGGgOd5eikHz1oRSbcRYxk1ECLRIF
EVM9acPZmvG9/apBMsKE3pCE641ef9ezrzVlnJ0wB19D1H7ekxlYJQ==
=IckQ
-----END PGP SIGNATURE-----
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
