
After go1.16, go will use module mode by default, even when the repository is checked out under GOPATH or in a one-off directory. Add go.mod, go.sum to keep this repo buildable without opting out of the module mode. > go mod init github.com/mmcgrana/gobyexample > go mod tidy > go mod vendor In module mode, the 'vendor' directory is special and its contents will be actively maintained by the go command. pygments aren't the dependency the go will know about, so it will delete the contents from vendor directory. Move it to `third_party` directory now. And, vendor the blackfriday package. Note: the tutorial contents are not affected by the change in go1.16 because all the examples in this tutorial ask users to run the go command with the explicit list of files to be compiled (e.g. `go run hello-world.go` or `go build command-line-arguments.go`). When the source list is provided, the go command does not have to compute the build list and whether it's running in GOPATH mode or module mode becomes irrelevant.
48 lines
813 B
Plaintext
48 lines
813 B
Plaintext
CREATE OR REPLACE FUNCTION something() RETURNS int4 AS
|
|
$x$
|
|
BEGIN
|
|
RETURN 42;
|
|
END
|
|
$x$
|
|
LANGUAGE 'plpgsql';
|
|
|
|
CREATE FUNCTION pymax (a integer, b integer)
|
|
RETURNS integer
|
|
AS $$
|
|
if a > b:
|
|
return a
|
|
return b
|
|
$$ language plpythonu;
|
|
|
|
CREATE FUNCTION nested_lexers (a integer, b integer)
|
|
$function$
|
|
BEGIN
|
|
SELECT ($1 ~ $q$[\t\r\n\v\\]$q$);
|
|
END;
|
|
$function$
|
|
LANGUAGE sql;
|
|
|
|
CREATE OR REPLACE FUNCTION measurement_insert_trigger()
|
|
RETURNS TRIGGER AS $$
|
|
BEGIN
|
|
<<test>>
|
|
INSERT INTO measurement_y2008m01 VALUES (NEW.*);
|
|
RETURN NULL;
|
|
END;
|
|
$$
|
|
LANGUAGE plpgsql;
|
|
|
|
-- As returned by pg_dump
|
|
CREATE FUNCTION test_function() RETURNS integer
|
|
LANGUAGE plpgsql STABLE STRICT
|
|
AS $$
|
|
begin
|
|
return 42;
|
|
end
|
|
$$;
|
|
|
|
-- Unicode names and strings
|
|
SELECT U&'\0441\043B\043E\043D'
|
|
FROM U&"\0441\043B\043E\043D";
|
|
|