I think if it could be done in a reasonably aesthetic way in psql that
would satisfy many people, without any need to disturb the backend,
which Tom objects to.
That's a big "if", IMNSHO :-).
I'd hate to see this dropped, though
cheers
andrew
Bruce Momjian wrote:
>I assume we never came to a final conclusion on how to do CREATE
>FUNCTION without double-quoting.
>
>---------------------------------------------------------------------------
>
>Tom Lane wrote:
>
>
>>Andrew Dunstan <andrew@dunslane.net> 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
>>
>>
>>
>
>
>