--On 25. Januar 2010 09:30:56 -0500 Robert Haas <[email protected]>
wrote:
This will turn into
another setting like search_path and standard_conforming_strings that
can break working code if the actual value doesn't match the
anticipated value. I can't figure out why someone would want to use
this even if we had it.
Hmm, even search_path is currently more strict than default_do_language
when used interactively:
be...@localhost:bernd #= SET search_path TO 'nonexistingschema';
ERROR: schema "nonexistingschema" does not exist
be...@localhost:bernd #= SET default_do_language TO 'blabla';
SET
Doesn't make sense to me...
--
Thanks
Bernd
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
