Because that's what I originally did and you shot it down as a bad
patch because you thought it wasn't in PostgreSQL's interest to filter
what we showed the user.
I'm still unconvinced on that, actually ... but it beats the heck out of
filtering everything not in your search path ...
Tom Lane [EMAIL PROTECTED] writes:
What happens if getenv(HOME) returns NULL?
Yeah, the strdup fails. I'll take it out to fix that.
You also need to think about Windows
Can I just ifndef WIN32 and not think about it? I'm not sure how that would
work either.
Finally, couldn't we reduce the
Zach Irmen said:
Tom Lane [EMAIL PROTECTED] writes:
What happens if getenv(HOME) returns NULL?
Yeah, the strdup fails. I'll take it out to fix that.
You also need to think about Windows
Can I just ifndef WIN32 and not think about it? I'm not sure how that
would work either.
If we are
Zach Irmen said:
Tom Lane [EMAIL PROTECTED] writes:
What happens if getenv(HOME) returns NULL?
Yeah, the strdup fails. I'll take it out to fix that.
You also need to think about Windows
Can I just ifndef WIN32 and not think about it? I'm not sure how that
would work either.
If we are
Andrew Dunstan [EMAIL PROTECTED] writes:
Zach Irmen said:
Can I just ifndef WIN32 and not think about it? I'm not sure how that
would work either.
If we are going to have a Windows port I don't think we should treat it as
a poor cousin.
I guess I was thinking more about if it should be
I think the original complaint was misguided and we should not do
anything about it. IIRC the complaint amounted to I have
hundreds of schemas and it annoys me that \dn shows them all.
How is this different from putting hundreds of tables into one
schema and then being annoyed because
