I assume we never came to a final conclusion on how to do CREATE FUNCTION without double-quoting.
--------------------------------------------------------------------------- Tom Lane wrote: > Andrew Dunstan <[EMAIL PROTECTED]> writes: > > In that case, though, the solution will presumably look at least a bit > > different from those discussed so far in this thread. Or would you have > > psql detect that in place of a string there was "stdin" or whatever and > > then replace it with the inline string before passing it to the backend? > > Please see the archives. I think that what was being discussed was > something along the lines of > > foo=> CREATE FUNCTION myfunc(...) RETURNS ... AS > foo=> \beginliteral > foo'> type my function definition here > foo'> and here > foo'> \endliteral > foo-> LANGUAGE plpgsql; > > and psql would proceed to quotify whatever you entered between > the two backslash commands. (Notice this could be used for any > string-literal entry problem, not only CREATE FUNCTION.) I'm fuzzy on > the details though; this may not have been the best idea presented. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend > -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
