The case is pretty simple. Slony expects fully quoted, case sensitive
specification of object names as they appear in pg_class.relname. As a
PostgreSQL DBA you are expected to know what is stored in that field for
a given table in your schema and how to specify it.
Jan
On 10/26/2005 8:14 AM, Philip Yarra wrote:
On Wed, 26 Oct 2005 08:52 pm, Andrew Sullivan wrote:
It makes no difference if it's a corner case. Slony is supposed to
provide generic support, which means we _have_ to support this.
Perhaps we mean different things by "corner case". I mean this:
http://en.wikipedia.org/wiki/Corner_case
As in, something we don't reasonably expect people to try to do. I think
creating table-names in the same DB in the same schema that are
differentiated only by the case of the name is unreasonable.
I'd be happy enough if the solution was simply to allow the perl tools to
generate usable output for the common case (and yes, maintain generic support
for people who really want account, ACCOUNT and aCcOuNt to describe three
different tables).
Right. It appears to me that this is a documentation issue.
What do you plan to put in the documentation? "Warning: table-names may not be
recognised using the same names as you used in your SQL script to create
them."
It just seems to me to make life one little bit harder than it needs to be, in
what must surely be the most common case (no pun intended).
Regards, Philip.
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== [EMAIL PROTECTED] #
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
