2000-01-19 00:30:24 +01:00
|
|
|
/*
|
|
|
|
|
* psql - the PostgreSQL interactive terminal
|
|
|
|
|
*
|
2018-01-03 05:30:12 +01:00
|
|
|
* Copyright (c) 2000-2018, PostgreSQL Global Development Group
|
2000-01-19 00:30:24 +01:00
|
|
|
*
|
2010-09-20 22:08:53 +02:00
|
|
|
* src/bin/psql/command.h
|
2000-01-19 00:30:24 +01:00
|
|
|
*/
|
1999-11-04 22:56:02 +01:00
|
|
|
#ifndef COMMAND_H
|
|
|
|
|
#define COMMAND_H
|
|
|
|
|
|
2016-03-24 23:27:28 +01:00
|
|
|
#include "fe_utils/print.h"
|
2016-03-25 01:28:47 +01:00
|
|
|
#include "fe_utils/psqlscan.h"
|
2018-03-22 15:42:03 +01:00
|
|
|
#include "fe_utils/conditional.h"
|
1999-11-04 22:56:02 +01:00
|
|
|
|
|
|
|
|
|
1999-11-05 00:14:30 +01:00
|
|
|
typedef enum _backslashResult
|
|
|
|
|
{
|
2006-10-04 02:30:14 +02:00
|
|
|
PSQL_CMD_UNKNOWN = 0, /* not done parsing yet (internal only) */
|
|
|
|
|
PSQL_CMD_SEND, /* query complete; send off */
|
|
|
|
|
PSQL_CMD_SKIP_LINE, /* keep building query */
|
|
|
|
|
PSQL_CMD_TERMINATE, /* quit program */
|
|
|
|
|
PSQL_CMD_NEWEDIT, /* query buffer was changed (e.g., via \e) */
|
|
|
|
|
PSQL_CMD_ERROR /* the execution of the backslash command
|
1999-11-05 00:14:30 +01:00
|
|
|
* resulted in an error */
|
2000-04-12 19:17:23 +02:00
|
|
|
} backslashResult;
|
1999-11-05 00:14:30 +01:00
|
|
|
|
|
|
|
|
|
2004-02-19 20:40:09 +01:00
|
|
|
extern backslashResult HandleSlashCmds(PsqlScanState scan_state,
|
Support \if ... \elif ... \else ... \endif in psql scripting.
This patch adds nestable conditional blocks to psql. The control
structure feature per se is complete, but the boolean expressions
understood by \if and \elif are pretty primitive; basically, after
variable substitution and backtick expansion, the result has to be
"true" or "false" or one of the other standard spellings of a boolean
value. But that's enough for many purposes, since you can always
do the heavy lifting on the server side; and we can extend it later.
Along the way, pay down some of the technical debt that had built up
around psql/command.c:
* Refactor exec_command() into a function per command, instead of
being a 1500-line monstrosity. This makes the file noticeably longer
because of repetitive function header/trailer overhead, but it seems
much more readable.
* Teach psql_get_variable() and psqlscanslash.l to suppress variable
substitution and backtick expansion on the basis of the conditional
stack state, thereby allowing removal of the OT_NO_EVAL kluge.
* Fix the no-doubt-once-expedient hack of sometimes silently substituting
mainloop.c's previous_buf for query_buf when calling HandleSlashCmds.
(It's a bit remarkable that commands like \r worked at all with that.)
Recall of a previous query is now done explicitly in the slash commands
where that should happen.
Corey Huinker, reviewed by Fabien Coelho, further hacking by me
Discussion: https://postgr.es/m/CADkLM=c94OSRTnat=LX0ivNq4pxDNeoomFfYvBKM5N_xfmLtAA@mail.gmail.com
2017-03-30 18:59:11 +02:00
|
|
|
ConditionalStack cstack,
|
|
|
|
|
PQExpBuffer query_buf,
|
|
|
|
|
PQExpBuffer previous_buf);
|
1999-11-05 00:14:30 +01:00
|
|
|
|
2015-12-08 20:04:08 +01:00
|
|
|
extern int process_file(char *filename, bool use_relative_path);
|
1999-11-05 00:14:30 +01:00
|
|
|
|
2003-06-28 02:12:40 +02:00
|
|
|
extern bool do_pset(const char *param,
|
1999-11-05 00:14:30 +01:00
|
|
|
const char *value,
|
2000-04-12 19:17:23 +02:00
|
|
|
printQueryOpt *popt,
|
1999-11-05 00:14:30 +01:00
|
|
|
bool quiet);
|
2001-10-28 07:26:15 +01:00
|
|
|
|
2010-02-16 22:07:01 +01:00
|
|
|
extern void connection_warnings(bool in_startup);
|
2008-07-01 02:08:18 +02:00
|
|
|
|
2003-06-28 02:12:40 +02:00
|
|
|
extern void SyncVariables(void);
|
|
|
|
|
|
|
|
|
|
extern void UnsyncVariables(void);
|
|
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* COMMAND_H */
|
