Shachar,
I've been giving this some more thought. Here are my contributions:
1. Setting should be on a per-database level. A per-server option is not
good enough, and a per-session option is too difficult to implement,
with no apparent justifiable return.
I disagree with this. I think
Josh Berkus wrote:
I also didn't follow the discussion of why a client-side implementation was
technically impossible; this seems like the most obvious course to me, and to
have *considerable* benefit.It's also consistent with our other statement
variables, such as datestyle, which are all
Shachar,
I think the concensus was that the runtime part was aprox. four lines
where the case folding currently takes place. Obviously, you would have
to get a var, and propogate that var to that place, but not actually
change program flow.
That's only if you ignore the system catalogs
Josh Berkus wrote:
Shachar,
I think the concensus was that the runtime part was aprox. four lines
where the case folding currently takes place. Obviously, you would have
to get a var, and propogate that var to that place, but not actually
change program flow.
That's only if you ignore
I'm opening a new thread, as the previous one was too nested, and
contained too much emotions.
I'll start by my understanding of a summary of the thread so far. The
solution we are seeking would have to satisfy the following conditions:
1. Setting should be on a per-database level. A per-server
