Dimitri Fontaine <[email protected]> writes:
> Tom Lane <[email protected]> writes:
>> If you think "cmdtrigger" isn't a good name maybe you should have
>> picked a different one to start with.
> Well, I think it's a good internal name. I'm not too sure about exposing
> it, the only reason why it's a good name is because it's a single not
> too long word, after all. Not very âSQLishâ.
> I'm putting cmdtrigger as the user visible name in the next version of
> the patch, if you come up with something potentially more user friendly
> feel free to suggest.
How about "commandtrigger" or "command_trigger"? Typing a few more
characters in this context doesn't seem like a deal-breaker to me.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
