52 Commits (d9572c4e3b474031060189050e14ef384b94e001)

Author	SHA1	Message	Date
Tom Lane	6cef5d2549	Operators live in namespaces. CREATE/DROP/COMMENT ON OPERATOR take ... qualified operator names directly, for example CREATE OPERATOR myschema.+ ( ... ). To qualify an operator name in an expression you need to write OPERATOR(myschema.+) (thanks to Peter for suggesting an escape hatch). I also took advantage of having to reformat pg_operator to fix something that'd been bugging me for a while: mergejoinable operators should have explicit links to the associated cross-data-type comparison operators, rather than hardwiring an assumption that they are named < and >.	24 years ago
Tom Lane	71dc300a37	The contents of command.c, creatinh.c, define.c, remove.c and rename.c ... have been divided according to the type of object manipulated - so ALTER TABLE code is in tablecmds.c, aggregate commands in aggregatecmds.c and so on. A few common support routines remain in define.c (prototypes in src/include/commands/defrem.h). No code has been changed except for includes to reflect the new files. The prototypes for aggregatecmds.c, functioncmds.c, operatorcmds.c, and typecmds.c remain in src/include/commands/defrem.h. From John Gray <jgray@azuli.co.uk>	24 years ago