polserver/testsuite/pol/testpkgs/sql/setup.src

use os;

include "testutil";
var res := GetEnvironmentVariable( "POLCORE_TESTSQL" );
if ( res != "1" )
  syslog( "NO SQL TESTS", 0 );
  return IGNORE_TEST;
else
  return 1;
endif
SQL non default port, escape string (#629) * added sql tests (linux only) * add mysql_escape_string module function its now possible to define a port for sql connection. (0 means default sql port like before) * escape string can fail, return error in this case * rebuild antlr * added docs 2024-03-10 14:31:30 +01:00			`use os;`

			`include "testutil";`
			`var res := GetEnvironmentVariable( "POLCORE_TESTSQL" );`
			`if ( res != "1" )`
			`syslog( "NO SQL TESTS", 0 );`
			`return IGNORE_TEST;`
			`else`
			`return 1;`
Format testsuite scripts, pol-core support modules (#713) * Format escript testsuite * Manual formatting for escript testsuite - Add format-off to places where formatter does what it should, but we don't like the results - Manually change places where formatter outputs weird things _without_ format-off, so next format-all would show changes if not fixed * Update .err files; add update_err.py helper script Use the format `:line:col: message` for all .err file checks. This allows us to change the file names without needing to edit the .err contents. Note that `in/inc0{1,2}.err` need have error messages between POSIX and Windows, so their messages are a bit more "generic" than the other errs. * Format pol testsuite * Manual formatting for pol testsuite * Format pol-core modules * Manual formatting for pol-core modules * Additional format pol-core modules Use FormatterLineWidth=10000 since module functions must be on one line because of the parse_modules target * Address Discord comments - Support multi-line module function declarations in parse_modules * Format on df07831 2024-10-04 10:29:55 +02:00			`endif`