Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
65decc34
Commit
65decc34
authored
Feb 07, 1999
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Allow psql to do \p\g. Ingres does it, why not us?
parent
48fd9a2c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
40 additions
and
17 deletions
+40
-17
src/bin/psql/psql.c
src/bin/psql/psql.c
+40
-17
No files found.
src/bin/psql/psql.c
View file @
65decc34
...
...
@@ -7,7 +7,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/bin/psql/Attic/psql.c,v 1.16
8 1999/02/03 21:17:44
momjian Exp $
* $Header: /cvsroot/pgsql/src/bin/psql/Attic/psql.c,v 1.16
9 1999/02/07 02:56:53
momjian Exp $
*
*-------------------------------------------------------------------------
*/
...
...
@@ -1753,10 +1753,10 @@ do_shell(const char *command)
/*
* HandleSlashCmds:
*
* Handles all the different commands that start with \
db_ptr is a pointer to
*
the TgDb* structure line is the current input line prompt_ptr is a pointer
*
to the prompt string, a pointer is used because the prompt can be
used
* with a connection to a new database.
* Handles all the different commands that start with \
*
db_ptr is a pointer to the TgDb* structure line is the current input
*
line prompt_ptr is a pointer to the prompt string, a pointer is
used
*
because the prompt can be used
with a connection to a new database.
* Returns a status:
* 0 - send currently constructed query to backend (i.e. we got a \g)
* 1 - skip processing of this line, continue building up query
...
...
@@ -2690,22 +2690,45 @@ MainLoop(PsqlSettings *pset, char *query, FILE *source)
if
(
!
in_quote
&&
query_start
[
0
]
==
'\\'
)
{
slashCmdStatus
=
HandleSlashCmds
(
pset
,
query_start
,
query
);
if
(
slashCmdStatus
==
CMD_SKIP_LINE
)
/* handle \p\g and other backslash combinations */
while
(
query_start
[
0
]
!=
'\0'
)
{
if
(
query
[
0
]
==
'\0'
)
paren_level
=
0
;
free
(
line
);
continue
;
char
hold_char
;
#ifndef WIN32
/* I believe \w \dos\system\x would cause a problem */
/* do we have '\p\g' or '\p \g' ? */
if
(
strlen
(
query_start
)
>
2
&&
query_start
[
2
+
strspn
(
query_start
+
2
,
"
\t
"
)]
==
'\\'
)
{
hold_char
=
query_start
[
2
+
strspn
(
query_start
+
2
,
"
\t
"
)];
query_start
[
2
+
strspn
(
query_start
+
2
,
"
\t
"
)]
=
'\0'
;
}
else
/* spread over #endif */
#endif
hold_char
=
'\0'
;
slashCmdStatus
=
HandleSlashCmds
(
pset
,
query_start
,
query
);
if
(
slashCmdStatus
==
CMD_SKIP_LINE
&&
!
hold_char
)
{
if
(
query
[
0
]
==
'\0'
)
paren_level
=
0
;
break
;
}
if
(
slashCmdStatus
==
CMD_TERMINATE
)
break
;
query_start
+=
strlen
(
query_start
);
if
(
hold_char
)
query_start
[
0
]
=
hold_char
;
}
free
(
line
);
/* They did \q, leave the loop */
if
(
slashCmdStatus
==
CMD_TERMINATE
)
{
free
(
line
);
break
;
}
free
(
line
);
}
else
if
(
strlen
(
query
)
+
strlen
(
query_start
)
>
MAX_QUERY_BUFFER
)
{
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment