You can’t declare variables in a view. Could you make it into a function or stored procedure? Edit – you might also be able to put something into a CTE (Common Table Expression) and keep it as a view. e.g. WITH conditions as ( … do the STUFF here ) SELECT blah FROM blah INNER … Read more
Postgresql historically doesn’t support procedural code at the command level – only within functions. However, in Postgresql 9, support has been added to execute an inline code block that effectively supports something like this, although the syntax is perhaps a bit odd, and there are many restrictions compared to what you can do with SQL … Read more
Any use of var foo in a function will scope foo to that function. It doesn’t matter where in the function this takes place as var declarations are hoisted. Additional uses of var foo in the same function are syntactically legal but will have no effect as the variable is already scoped to that function. … Read more
MySQL has two different types of variable: local variables (which are not prefixed by @) are strongly typed and scoped to the stored program block in which they are declared. Note that, as documented under DECLARE Syntax: DECLARE is permitted only inside a BEGIN … END compound statement and must be at its start, before … Read more
A variable, as you can guess from the name, varies over time. If it doesn’t vary, there is “no loss”. When you tell the compiler that the value will not change, the compiler can do a whole bunch of optimizations, like directly inlining the value and never allocating any space for the constant on the … Read more
Yes, it is if you want them all to point to the same object in memory, but most likely you want them to be individual arrays so that if one mutates, the others are not affected. If you do not want them all to point to the same object, do var one = [], two … Read more
The global declaration is when you declare that times is global def timeit(): global times # <- global declaration # … If a variable is declared global, it can’t be used before the declaration. In this case, I don’t think you need the declaration at all, because you’re not assigning to times, just modifying it.
The full line from your example is: #!/bin/env node This simply means that the script should be executed with the first executable named ‘node’ that’s found in your current PATH. The shebang (#!) at the start means execute the script with what follows. /bin/env is a standard unix program that looks at your current environment. … Read more
Check out the documentation on working with 3rd party modules. How to write the declaration depends a lot on how the module was written and what it exports. The example you’ve given is a CommonJS module (module.exports = …) which is not really a valid ES6 module, because ES6 cannot export a function as the … Read more