+ class="parameter">username instead of the default.
+ (You must have permission to do so, of course.)
Performs a variable assignment, like the \set
- internal command. Note that you must separate name and value,
- if any, by an equal sign on the command line. To unset a
- variable, leave off the equal sign. To just set a variable
- without a value, use the equal sign but leave off the value.
- These assignments are done during a very early stage of
- start-up, so variables reserved for internal purposes might get
- overwritten later.
+ internal command. Note that you must separate name and value, if
+ any, by an equal sign on the command line. To unset a variable,
+ leave off the equal sign. To just set a variable without a value,
+ use the equal sign but leave off the value. These assignments are
+ done during a very early stage of start-up, so variables reserved
+ for internal purposes might get overwritten later.
-W, --password
- Requests that
psql should prompt for a
password - before connecting to a database. This will remain set for the entire
- session, even if you change the database connection with the meta-command
- \connect .
+ Requests that
psql should prompt for a
+ password before connecting to a database. This will remain set for
+ the entire session, even if you change the database connection
+ with the meta-command \connect .
- In the current version,
psql automatically issues a
- password prompt whenever the backend requests password authentication.
- Because this is currently based on a hack, the automatic
- recognition might mysteriously fail, hence this option to force a prompt.
- If no password prompt is issued and the backend requires password authentication
- the connection attempt will fail.
+ In the current version,
psql + automatically issues a password prompt whenever the backend
+ requests password authentication. Because this is currently based
+ on a hack, the automatic recognition might mysteriously fail,
+ hence this option to force a prompt. If no password prompt is
+ issued and the backend requires password authentication the
+ connection attempt will fail.
-x, --expanded
- Turns on extended row format mode. This is equivalent to the command
- \x .
+ Turns on extended row format mode. This is equivalent to the
+ command \x .
-?, --help
- Shows help about
psql command line arguments.
+ Shows help about
psql command line
+ arguments.
Variables
-
psql provides variable substitution features
- similar to common Unix command shells. This feature is new and not very
- sophisticated, yet, but there are plans to expand it in the future.
- Variables are simply name/value
- pairs, where the value can be any string of any length. To set variables,
- use the
psql meta-command
\set :
+
psql provides variable substitution
+ features similar to common Unix command shells. This feature is new
+ and not very sophisticated, yet, but there are plans to expand it in
+ the future. Variables are simply name/value pairs, where the value
+ can be any string of any length. To set variables, use the
+ \set :
testdb=> \set foo bar
- sets the variable foo
to the value bar
. To retrieve
- the content of the variable, precede the name with a colon and use it
- as the argument of any slash command:
+ sets the variable foo
to the value
+ bar
. To retrieve the content of the variable, precede
+ the name with a colon and use it as the argument of any slash
+ command:
testdb=> \echo :foo
bar
- The arguments of \set are subject to the same substitution
- rules as with other commands. Thus you can construct interesting references
- such as \set :foo 'something' and get soft
- links or
variable variables
of
Perl - or
PHP fame, respectively.
- Unfortunately (or fortunately?), there is no way to do anything useful
- with these constructs. On the
- other hand, \set bar :foo is a perfectly valid way to copy
- a variable.
+ The arguments of \set are subject to the same
+ substitution rules as with other commands. Thus you can construct
+ interesting references such as \set :foo
+ 'something' and get soft links
or
+
variable variables
of
Perl + respectively. Unfortunately (or fortunately?), there is no way to do
+ anything useful with these constructs. On the other hand,
+ \set bar :foo is a perfectly valid way to copy a
+ variable.
- If you call \set without a second argument, the variable is simply
- set, but has no value. To unset (or delete) a variable, use the command
- \unset .
+ If you call \set without a second argument, the
+ variable is simply set, but has no value. To unset (or delete) a
+ variable, use the command \unset .
-
psql 's internal variable names can
consist of - letters, numbers, and underscores in any order and any number of them.
- A number of regular variables are treated specially by
psql .
- They indicate certain option settings that can be changed at run time
- by altering the value of the variable or represent some state of the application.
- Although you can use these
- variables for any other purpose, this is not recommended, as the
- program behavior might grow really strange really quickly.
- By convention, all specially treated variables consist of all upper-case letter s
- (and possibly numbers and underscores). To ensure maximum compatibility in the
- future, avoid such variables.
- A list of all specially treated variables follows.
+
psql 's internal variable names can
+ consist of letters, numbers, and underscores in any order and any
+ number of them. A number of regular variables are treated specially
+ by
psql . They indicate certain option
+ settings that can be changed at run time by altering the value of
+ the variable or represent some state of the application. Although
+ you can use these variables for any other purpose, this is not
+ recommended, as the program behavior might grow really strange
+ really quickly. By convention, all specially treated variable s
+ consist of all upper-case letters (and possibly numbers and
+ underscores). To ensure maximum compatibility in the future, avoid
+ such variables. A list of all specially treated variables follows.
DBNAME
- The name of the database you are currently connected to. This is set every time
- you connect to a database (including program start-up), but can be unset.
+ The name of the database you are currently connected to. This is
+ set every time you connect to a database (including program
+ start-up), but can be unset.
ECHO
- If set to all
, all lines entered or from a script
- are written to the standard output before they
- are parsed or executed. To specify this on program start-up, use the switch
- -a . If set to queries
,
-
psql merely prints all queries as they are sent to the
- backend. The option for this is -e .
+ If set to all
, all lines
+ entered or from a script are written to the standard output
+ before they are parsed or executed. To specify this on program
+ start-up, use the switch -a . If set to
+ queries
,
+
psql merely prints all queries as
+ they are sent to the backend. The option for this is
+ -e .
ECHO_HIDDEN
- When this variable is set and a backslash command queries the database, the query
- is first shown. This way you can study the
PostgreSQL - internals and provide similar functionality in your own programs. If you set the
- variable to the value noexec
, the queries are just shown but are
- not actually sent to the backend and executed.
+ When this variable is set and a backslash command queries the
+ database, the query is first shown. This way you can study the
+
PostgreSQL internals and provide
+ similar functionality in your own programs. If you set the
+ variable to the value noexec
, the queries are
+ just shown but are not actually sent to the backend and
+ executed.
ENCODING
- The current client multibyte encoding. If you are not set up to use
- multibyte characters, this variable will always contain
+ The current client multibyte encoding. If you are not set up to
+ use multibyte characters, this variable will always contain
SQL_ASCII
.
HISTCONTROL
- If this variable is set to ignorespace , lines which begin with a
- space are not entered into the history list. If set to a value of
- ignoredups , lines matching the previous history line are not
- entered. A value of ignoreboth combines the two
- options. If unset, or if set to any other value than those above, all lines read
- in interactive mode are saved on the history list.
+ If this variable is set to ignorespace ,
+ lines which begin with a space are not entered into the history
+ list. If set to a value of ignoredups , lines
+ matching the previous history line are not entered. A value of
+ ignoreboth combines the two options. If
+ unset, or if set to any other value than those above, all lines
+ read in interactive mode are saved on the history list.
- This feature was shamelessly plagiarized from
bash .
+ This feature was shamelessly plagiarized from
HISTSIZE
- The number of commands to store in the command history.
- The default value is 500.
+ The number of commands to store in the command history. The
+ default value is 500.
- This feature was shamelessly plagiarized from
bash .
+ This feature was shamelessly plagiarized from
HOST
- The database server host you are currently connected to. This is set every time
- you connect to a database (including program start-up), but can be unset.
+ The database server host you are currently connected to. This is
+ set every time you connect to a database (including program
+ start-up), but can be unset.
IGNOREEOF
- If unset, sending an EOF character (usually Control-D) to an interactive session of
-
psql will terminate the application.
- If set to a numeric value, that many EOF characters are ignored before the application
- terminates. If the variable is set but has no numeric value, the default is 10.
+ If unset, sending an EOF character (usually Control-D) to an
+ interactive session of
psql will
+ terminate the application. If set to a numeric value, that many
+ EOF characters are ignored before the application terminates.
+ If the variable is set but has no numeric value, the default is
+ 10.
- This feature was shamelessly plagiarized from
bash .
+ This feature was shamelessly plagiarized from
LASTOID
- The value of the last affected oid, as returned from an INSERT
- or lo_insert command. This variable is only guaranteed to be
- valid until after the result of the next
SQL command has been
- displayed.
+ The value of the last affected oid, as returned from an
+ INSERT or lo_insert
+ command. This variable is only guaranteed to be valid until
+ after the result of the next
SQL command has
+ been displayed.
LO_TRANSACTION
- If you use the
PostgreSQL large object
- interface to specially store data that does not fit into one tuple,
- all the operations must be contained in a transaction block. (See the
- documentation of the large object interface for more information.) Since
-
psql has no way to tell if you already
- have a transaction in progress when you call one of its internal
- commands (\lo_export , \lo_import ,
- \lo_unlink ) it must take some arbitrary action. This
- action could either be to roll back any transaction that might already
- be in progress, or to commit any such transaction, or to do nothing at
- all. In the last case you must provide your own
- BEGIN TRANSACTION /COMMIT block or
- the results will be unpredictable (usually resulting in the desired
- action's not being performed in any case).
+ If you use the
PostgreSQL large
+ object interface to specially store data that does not fit into
+ one tuple, all the operations must be contained in a transaction
+ block. (See the documentation of the large object interface for
+ more information.) Since
psql has no
+ way to tell if you already have a transaction in progress when
+ you call one of its internal commands
+ (\lo_export , \lo_import ,
+ \lo_unlink ) it must take some arbitrary
+ action. This action could either be to roll back any transaction
+ that might already be in progress, or to commit any such
+ transaction, or to do nothing at all. In the last case you must
+ provide your own BEGIN
+ TRANSACTION/COMMIT block or the
+ results will be unpredictable (usually resulting in the desired
+ action's not being performed in any case).
To choose what you want to do you set this variable to one of
- rollback
, commit
, or nothing
.
- The default is to roll back the transaction. If you just want to load one
- or a few objects this is fine. However, if you intend to transfer many
- large objects, it might be advisable to provide one explicit transaction
- block around all commands.
+ rollback
, commit
, or
+ nothing
. The default is to roll back the
+ transaction. If you just want to load one or a few objects this
+ is fine. However, if you intend to transfer many large objects,
+ it might be advisable to provide one explicit transaction block
+ around all commands.
ON_ERROR_STOP
- By default, if non-interactive scripts encounter an error, such as a
- malformed
SQL query or internal meta-command,
- processing continues. This has been the traditional behavior of
-
psql but it is sometimes not desirable. If this variable
- is set, script processing will immediately terminate. If the script was
- called from another script it will terminate in the same fashion.
- If the outermost script was not called from an interactive
psql - session but rather using the
-f option,
psql - will return error code 3, to distinguish this case from fatal
- error conditions (error code 1).
+ By default, if non-interactive scripts encounter an error, such
+ as a malformed
SQL query or internal
+ meta-command, processing continues. This has been the
+ traditional behavior of
psql but it
+ is sometimes not desirable. If this variable is set, script
+ processing will immediately terminate. If the script was called
+ from another script it will terminate in the same fashion. If
+ the outermost script was not called from an interactive
+
psql session but rather using the
+ return error code 3, to distinguish this case from fatal error
+ conditions (error code 1).
PORT
- The database server port to which you are currently connected. This is set every time
- you connect to a database (including program start-up), but can be unset.
+ The database server port to which you are currently connected.
+ This is set every time you connect to a database (including
+ program start-up), but can be unset.
PROMPT1 , PROMPT2 , PROMPT3
- These specify what the prompt
psql issues is - supposed to look like. See
-
- below.
+ These specify what the prompt
psql + issues is supposed to look like. See
+ linkend="APP-PSQL-prompting"
+ endterm="APP-PSQL-prompting-title"> below.
QUIET
- This variable is equivalent to the command line option -q .
- It is probably not too useful in interactive mode.
+ This variable is equivalent to the command line option
+ -q . It is probably not too useful in
+ interactive mode.
SINGLELINE
- This variable is set by the command line option -S . You
- can unset or reset it at run time.
+ This variable is set by the command line option
+ -S . You
SINGLESTEP
- This variable is equivalent to the command line option -s .
+ This variable is equivalent to the command line option
+ -s .
USER
- The database user you are currently connected as. This is set every time
- you connect to a database (including program start-up), but can be unset.
+ The database user you are currently connected as. This is set
+ every time you connect to a database (including program
+ start-up), but can be unset.
- An additional useful feature of
psql variables
- is that you can substitute (interpolate
) them into
- regular
SQL statements. The syntax for this is again to prepend
- the variable name with a colon (: ).
+ An additional useful feature of
psql + variables is that you can substitute (interpolate
)
+ them into regular
SQL statements. The syntax for
+ this is again to prepend the variable name with a colon
+ (: ).
testdb=> \set foo 'my_table'
testdb=> SELECT * FROM :foo;
- would then query the table my_table . The value of the
- variable is copied literally, so it can even contain unbalanced quotes or
- backslash commands. You must make sure that it makes sense where you put it.
- Variable interpolation will not be performed into quoted
SQL - entities.
+ would then query the table my_table . The value of
+ the variable is copied literally, so it can even contain unbalanced
+ quotes or backslash commands. You must make sure that it makes sense
+ where you put it. Variable interpolation will not be performed into
- A popular application of this facility is to refer to the last inserted
-
OID in subsequent statements to build a foreign key
- scenario.
- Another possible use of this mechanism is to copy the contents of a file
- into a field. First load the file into a variable and then proceed as above.
+ A popular application of this facility is to refer to the last
+ inserted
OID in subsequent statements to build a
+ foreign key scenario. Another possible use of this mechanism is to
+ copy the contents of a file into a field. First load the file into a
+ variable and then proceed as above.
testdb=> \set content '\'' `cat my_file.txt` '\''
testdb=> INSERT INTO my_table VALUES (:content);
testdb=> \set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\''
- Observe the correct number of backslashes (6)! You can resolve it this way: After
-
psql has parsed this line, it passes
- sed -e "s/'/\\\'/g" < my_file.txt to the shell. The shell
- will do its own thing inside the double quotes and execute sed
- with the arguments -e and s/'/\\'/g .
- When
sed parses this it will replace the two
- backslashes with a single one and then do the substitution. Perhaps at
- one point you thought it was great that all Unix commands use the same
- escape character. And this is ignoring the fact that you might have to
- escape all backslashes as well because
SQL text constants
- are also subject to certain interpretations. In that case you might
- be better off preparing the file externally.
+ Observe the correct number of backslashes (6)! You can resolve it
+ this way: After
psql has parsed this
+ line, it passes sed -e "s/'/\\\'/g" < my_file.txt
+ to the shell. The shell will do its own thing inside the double
+ quotes and execute sed with the arguments
+ -e and s/'/\\'/g . When
+
sed parses this it will replace the two
+ backslashes with a single one and then do the substitution. Perhaps
+ at one point you thought it was great that all Unix commands use the
+ same escape character. And this is ignoring the fact that you might
+ have to escape all backslashes as well because
+
SQL text constants are also subject to certain
+ interpretations. In that case you might be better off preparing the
+ file externally.
- Since colons may legally appear in queries, the following rule applies: If the variable
- is not set, the character sequence colon+name
is not changed. In any
- case you can escape a colon with a backslash to protect it from interpretation.
- (The colon syntax for variables is standard
SQL for embedded
- query languages, such as
ecpg . The colon syntax for
- array slices and type casts are
PostgreSQL extensions,
- hence the conflict.)
+ Since colons may legally appear in queries, the following rule
+ applies: If the variable is not set, the character sequence
+ colon+name
is not changed. In any case you can escape
+ a colon with a backslash to protect it from interpretation. (The
+ colon syntax for variables is standard
SQL for
+ embedded query languages, such as
ecpg .
+ The colon syntax for array slices and type casts are
+
PostgreSQL extensions, hence the
+ conflict.)
Prompting
- The prompts
psql issues can be customized to
- your preference. The three variables PROMPT1 , PROMPT2 ,
- and PROMPT3 contain strings and special escape sequences
- that describe the appearance of the prompt. Prompt 1 is the normal prompt
- that is issued when
psql requests a new query.
- Prompt 2 is issued when more input is expected during query input because
- the query was not terminated with a semicolon or a quote was not closed.
- Prompt 3 is issued when you run an
SQL COPY - command and you are expected to type in the tuples on the terminal.
+ The prompts
psql issues can be customized
+ to your preference. The three variables PROMPT1 ,
+ PROMPT2 , and PROMPT3 contain strings
+ and special escape sequences that describe the appearance of the
+ prompt. Prompt 1 is the normal prompt that is issued when
+
psql requests a new query. Prompt 2 is
+ issued when more input is expected during query input because the
+ query was not terminated with a semicolon or a quote was not closed.
+ Prompt 3 is issued when you run an
SQL + COPY command and you are expected to type in the
+ tuples on the terminal.
- The value of the respective prompt variable is printed literally, except where
- a percent sign (%
) is encountered. Depending on the next
- character, certain other text is substituted instead. Defined substitutions are:
+ The value of the respective prompt variable is printed literally,
+ except where a percent sign (%
) is encountered.
+ Depending on the next character, certain other text is substituted
+ instead. Defined substitutions are:
The full host name (with domain name) of the database server,
- or [local] if the connection is over a
- Unix domain socket, or
- [local:/dir/name ]>,
- if the Unix domain socket is not at the compiled in default
+ or [local] if the connection is over a Unix
+ domain socket, or
+
[local:/dir/name ]
+ >, if the Unix domain socket is not at the compiled in default
location.
The host name of the database server, truncated after the
- first dot, or [local] if the connection
- is over a Unix domain socket.
+ first dot, or [local] if the connection is
+ over a Unix domain socket.
%R
- In prompt 1 normally =
, but ^
if in single-line
- mode, and !
if the session is disconnected from the database
- (which can happen if \connect fails). In prompt 2 the
- sequence is replaced by -
, *
, a single quote,
- or a double quote, depending on whether
psql - expects more input because the query wasn't terminated yet, because you are
- inside a /* ... */ comment, or because you are inside
- a quote. In prompt 3 the sequence doesn't resolve to anything.
+
+ In prompt 1 normally =
, but ^
if
+ in single-line mode, and !
if the session is
+ disconnected from the database (which can happen if
+ \connect fails). In prompt 2 the sequence is
+ replaced by -
, *
, a single quote,
+ or a double quote, depending on whether
+
psql expects more input because the
+ query wasn't terminated yet, because you are inside a
+ /* ... */ comment, or because you are inside
+ a quote. In prompt 3 the sequence doesn't resolve to anything.
+
% digits
- If digits starts with
- 0x the rest of the characters are interpreted as a
- hexadecimal digit and the character with the corresponding code is
- substituted. If the first digit is 0 the characters are
- interpreted as on octal number and the corresponding character is
- substituted. Otherwise a decimal number is assumed.
+
+ If digits starts
+ with 0x the rest of the characters are
+ interpreted as a hexadecimal digit and the character with the
+ corresponding code is substituted. If the first digit is
+ 0 the characters are interpreted as on octal
+ number and the corresponding character is substituted. Otherwise
+ a decimal number is assumed.
+
%: name:
- The value of the
psql , variable
- class="parameter">name. See the section
-
- for details.
+
+ The value of the
psql , variable
+ name. See the
+ section
+ endterm="APP-PSQL-variables-title"> for details.
+
%` command`
- The output of command, similar to
- ordinary back-tick
substitution.
+
+ The output of
+ class="parameter">command, similar to ordinary
+ back-tick
substitution.
+
- To insert a percent sign into your prompt, write %% . The
- default prompts are equivalent to '%/%R%# ' for prompts 1
- and 2, and '>> ' for prompt 3.
+ To insert a percent sign into your prompt, write
+ %% . The default prompts are equivalent to
+ '%/%R%# ' for prompts 1 and 2, and
+ '>> ' for prompt 3.
- This feature was shamelessly plagiarized from
tcsh .
+ This feature was shamelessly plagiarized from
Miscellaneous
-
psql returns 0 to the shell if it
finished normally, - 1 if a fatal error of its own (out of memory, file not found) occurs, 2 if the
- connection to the backend went bad and the session is not interactive, and 3 if
- an error occurred in a script and the variable ON_ERROR_STOP was
- set.
+
psql returns 0 to the shell if it
+ finished normally, 1 if a fatal error of its own (out of memory,
+ file not found) occurs, 2 if the connection to the backend went bad
+ and the session is not interactive, and 3 if an error occurred in a
+ script and the variable ON_ERROR_STOP was s et.
- Before starting up,
psql attempts
- to read and execute commands from the file $HOME/.psqlrc . It
- could be used to set up the client or the server to taste (using the \set
- and SET commands).
+ Before starting up,
psql attempts to read
+ and execute commands from the file
+ $HOME/.psqlrc . It could be used to set up the
+ client or the server to taste (using the \set
+ and SET commands).
<acronym>GNU</acronym> readline
-
psql supports the readline and history libraries for
- convenient line editing and retrieval. The command history is stored in a file
- named .psql_history in your home directory and is reloaded when
- Tab-completion is also supported, although
- the completion logic makes no claim to be an
SQL parser.
- When available,
psql is automatically built to use these
- features. If for some reason you do not like the tab completion, you can turn if off
- by putting this in a file named .inputrc in your
- home directory:
+
psql supports the readline and history
+ libraries for convenient line editing and retrieval. The command
+ history is stored in a file named .psql_history
+ in your home directory and is reloaded when
+
psql starts up. Tab-completion is also
+ supported, although the completion logic makes no claim to be an
+
SQL parser. When available,
+
psql is automatically built to use these
+ features. If for some reason you do not like the tab completion, you
+ can turn if off by putting this in a file named
+ .inputrc in your home directory:
$if psql
set disable-completion on
$endif
- (This is not a
psql but a
readline - feature. Read its documentation for further details.)
+ (This is not a
psql but a
+
readline feature. Read its documentation
+ for further details.)
- If you have the readline library installed but
psql - does not seem to use it, you must make sure that
PostgreSQL 's
- top-level configure script finds it. configure
- needs to find both the library libreadline.a
- (or a shared library equivalent)
- and the header files readline.h and
- history.h (or readline/readline.h and
- readline/history.h ) in appropriate directories. If
- you have the library and header files installed in an obscure place you
- must tell configure about them, for example:
+ If you have the readline library installed but
+
psql does not seem to use it, you must
+ make sure that
PostgreSQL 's top-level
+ configure script finds it.
+ configure needs to find both the library
+ libreadline.a (or a shared library equivalent)
+ and the header files
+ readline.h and history.h
+ (or readline/readline.h and
+ readline/history.h ) in appropriate directories.
+ If you have the library and header files installed in an obscure
+ place you must tell configure about them, for
+ example:
$ ./configure --with-includes=/opt/gnu/include --with-libs=/opt/gnu/lib ...
- Then you have to recompile
psql (not
necessarily - the entire code tree).
+ Then you have to recompile
psql (not
+ necessarily the entire code tree).
- The
GNU readline library can be obtained from the
GNU - project's
FTP server at
ftp://ftp.gnu.org. + The
GNU readline library can be obtained from the
+
GNU project's
FTP server at
- This section only shows a few examples specific to
psql .
- If you want to learn
SQL or get familiar with
-
PostgreSQL , you might wish to read the Tutorial that
- is included in the distribution.
+ This section only shows a few examples specific to
+
psql . If you want to learn
+
SQL or get familiar with
+
PostgreSQL , you might wish to read the
+ Tutorial that is included in the distribution.
- The first example shows how to spread a query over several lines of input.
- Notice the changing prompt:
+ The first example shows how to spread a query over several lines of
+ input. Notice the changing prompt:
testdb=> CREATE TABLE my_table (
testdb(> first integer not null default 0,
testdb=> \set PROMPT1 '%n@%m %~%R%# '
peter@localhost testdb=>
- Let's assume you have filled the table with data and want to take a look at it:
+ Let's assume you have filled the table with data and want to take a
+ look at it:
peter@localhost testdb=> SELECT * FROM my_table;
first | second
(4 rows)
- You can make this table look differently by using the \pset
- command:
+ You can make this table look differently by using the
+ \pset
peter@localhost testdb=> \pset border 2
Border style is 2.
- In some earlier life
psql allowed the first
- argument to start directly after the (single-letter) command. For
- compatibility this is still supported to some extent but I am not
- going to explain the details here as this use is discouraged. But
- if you get strange messages, keep this in mind. For example
+ In some earlier life
psql allowed the
+ first argument to start directly after the (single-letter)
+ command. For compatibility this is still supported to some extent
+ but I am not going to explain the details here as this use is
+ discouraged. But if you get strange messages, keep this in mind.
+ For example
testdb=> \foo
Field separator is "oo",
-
psql only works smoothly with servers of the
- same version. That does not mean other combinations will fail outright,
- but subtle and not-so-subtle problems might come up.
+
psql only works smoothly with servers
+ of the same version. That does not mean other combinations will
+ fail outright, but subtle and not-so-subtle problems might come
+ up.
- Pressing Control-C during a copy in
(data sent to the
- server) doesn't show the most ideal of behaviors. If you get a message
- such as COPY state must be terminated first
,
- simply reset the connection by entering \c - - .
+ Pressing Control-C during a copy in
(data sent to
+ the server) doesn't show the most ideal of behaviors. If you get a
+ message such as COPY state must be terminated
+ first, simply reset the connection by entering \c
+ - -.
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/commands/copy.c,v 1.156 2002/05/21 22:59:00 tgl Exp $
+ * $Header: /cvsroot/pgsql/src/backend/commands/copy.c,v 1.157 2002/06/20 16:00:43 momjian Exp $
*
*-------------------------------------------------------------------------
*/
* the table.
*/
void
-DoCopy(const RangeVar *relation, bool binary, bool oids, bool from, bool pipe,
- char *filename, char *delim, char *null_print)
+DoCopy(const CopyStmt *stmt)
{
+ RangeVar *relation = stmt->relation;
+ char *filename = stmt->filename;
+ bool is_from = stmt->is_from;
+ bool pipe = (stmt->filename == NULL);
+ List *option;
+ DefElem *dbinary = NULL;
+ DefElem *doids = NULL;
+ DefElem *ddelim = NULL;
+ DefElem *dnull = NULL;
+ bool binary = false;
+ bool oids = false;
+ char *delim = "\t";
+ char *null_print = "\\N";
FILE *fp;
Relation rel;
- AclMode required_access = (from ? ACL_INSERT : ACL_SELECT);
+ AclMode required_access = (is_ from ? ACL_INSERT : ACL_SELECT);
AclResult aclresult;
+ /* Extract options from the statement node tree */
+ foreach(option, stmt->options)
+ {
+ DefElem *defel = (DefElem *) lfirst(option);
+
+ if (strcmp(defel->defname, "binary") == 0)
+ {
+ if (dbinary)
+ elog(ERROR, "COPY: conflicting options");
+ dbinary = defel;
+ }
+ else if (strcmp(defel->defname, "oids") == 0)
+ {
+ if (doids)
+ elog(ERROR, "COPY: conflicting options");
+ doids = defel;
+ }
+ else if (strcmp(defel->defname, "delimiter") == 0)
+ {
+ if (ddelim)
+ elog(ERROR, "COPY: conflicting options");
+ ddelim = defel;
+ }
+ else if (strcmp(defel->defname, "null") == 0)
+ {
+ if (dnull)
+ elog(ERROR, "COPY: conflicting options");
+ dnull = defel;
+ }
+ else
+ elog(ERROR, "COPY: option \"%s\" not recognized",
+ defel->defname);
+ }
+
+ if (dbinary)
+ binary = intVal(dbinary->arg);
+ if (doids)
+ oids = intVal(doids->arg);
+ if (ddelim)
+ delim = strVal(ddelim->arg);
+ if (dnull)
+ null_print = strVal(dnull->arg);
+
+ if (binary && ddelim)
+ elog(ERROR, "You can not specify the DELIMITER in BINARY mode.");
+
+ if (binary && dnull)
+ elog(ERROR, "You can not specify NULL in BINARY mode.");
+
/*
* Open and lock the relation, using the appropriate lock type.
*/
- rel = heap_openrv(relation, (from ? RowExclusiveLock : AccessShareLock));
+ rel = heap_openrv(relation, (is_ from ? RowExclusiveLock : AccessShareLock));
/* Check permissions. */
aclresult = pg_class_aclcheck(RelationGetRelid(rel), GetUserId(),
server_encoding = GetDatabaseEncoding();
#endif
- if (from)
+ if (is_ from)
{ /* copy from file to database */
if (rel->rd_rel->relkind != RELKIND_RELATION)
{
if (!pipe)
FreeFile(fp);
- else if (!from)
+ else if (!is_ from)
{
if (!binary)
CopySendData("\\.\n", 3, fp);
* transaction to ensure that updates will be committed before lock is
* released.
*/
- heap_close(rel, (from ? NoLock : AccessShareLock));
+ heap_close(rel, (is_ from ? NoLock : AccessShareLock));
}
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/commands/dbcommands.c,v 1.93 2002/06/18 17:27:57 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/commands/dbcommands.c,v 1.94 2002/06/20 16:00:43 momjian Exp $
*
*-------------------------------------------------------------------------
*/
*/
void
-createdb(CreatedbStmt *stmt)
+createdb(const CreatedbStmt *stmt)
{
char *nominal_loc;
char *alt_loc;
* Portions Copyright (c) 1994, Regents of the University of California
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/nodes/copyfuncs.c,v 1.189 2002/06/18 17:27:57 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/nodes/copyfuncs.c,v 1.190 2002/06/20 16:00:43 momjian Exp $
*
*-------------------------------------------------------------------------
*/
{
CopyStmt *newnode = makeNode(CopyStmt);
- newnode->binary = from->binary;
Node_Copy(from, newnode, relation);
- newnode->oids = from->oids;
- newnode->direction = from->direction;
+ newnode->is_from = from->is_from;
if (from->filename)
newnode->filename = pstrdup(from->filename);
- if (from->delimiter)
- newnode->delimiter = pstrdup(from->delimiter);
- if (from->null_print)
- newnode->null_print = pstrdup(from->null_print);
+ Node_Copy(from, newnode, options);
return newnode;
}
* Portions Copyright (c) 1994, Regents of the University of California
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/nodes/equalfuncs.c,v 1.136 2002/06/18 17:27:57 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/nodes/equalfuncs.c,v 1.137 2002/06/20 16:00:43 momjian Exp $
*
*-------------------------------------------------------------------------
*/
static bool
_equalCopyStmt(CopyStmt *a, CopyStmt *b)
{
- if (a->binary != b->binary)
- return false;
if (!equal(a->relation, b->relation))
return false;
- if (a->oids != b->oids)
- return false;
- if (a->direction != b->direction)
+ if (a->is_from != b->is_from)
return false;
if (!equalstr(a->filename, b->filename))
return false;
- if (!equalstr(a->delimiter, b->delimiter))
- return false;
- if (!equalstr(a->null_print, b->null_print))
+ if (!equal(a->options, b->options))
return false;
return true;
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/parser/gram.y,v 2.331 2002/06/19 15:40:58 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/parser/gram.y,v 2.332 2002/06/20 16:00:43 momjian Exp $
*
* HISTORY
* AUTHOR DATE MAJOR EVENT
%type alter_column_default
%type add_drop, drop_behavior, opt_drop_behavior
-%type createdb_opt_list
-%type createdb_opt_item
+%type createdb_opt_list, copy_opt_list
+%type createdb_opt_item, copy_opt_item
%type opt_lock, lock_type
%type opt_force, opt_or_replace
%type TriggerEvents
%type TriggerFuncArg
-%type relation_name, copy_file_name, copy_delimiter, copy_null,
+%type relation_name, copy_file_name,
database_name, access_method_clause, access_method, attr_name,
index_name, name, function_name, file_name
%type opt_interval
%type overlay_placing, substr_from, substr_for
-%type opt_binary, opt_ instead, opt_cursor
-%type opt_with_copy, index_opt_unique, opt_verbose, opt_full
+%type opt_instead, opt_cursor
+%type index_opt_unique, opt_verbose, opt_full
%type opt_freeze
+%type opt_binary, opt_oids, copy_delimiter
-%type copy_dirn, direction, reindex_type, drop_type,
+%type copy_from
+
+%type direction, reindex_type, drop_type,
opt_column, event, comment_type
%type fetch_how_many
CURRENT_TIMESTAMP, CURRENT_USER, CURSOR, CYCLE,
DATABASE, DAY_P, DEC, DECIMAL, DECLARE, DEFAULT,
- DEFERRABLE, DEFERRED, DEFINER, DELETE_P, DELIMITERS, DESC ,
- DISTINCT, DO, DOMAIN_P, DOUBLE, DROP,
+ DEFERRABLE, DEFERRED, DEFINER, DELETE_P, DELIMITER, DELIMITERS ,
+ DESC, DISTINCT, DO, DOMAIN_P, DOUBLE, DROP,
EACH, ELSE, ENCODING, ENCRYPTED, END_TRANS, ESCAPE, EXCEPT,
EXCLUSIVE, EXECUTE, EXISTS, EXPLAIN, EXTERNAL, EXTRACT,
/*****************************************************************************
*
* QUERY :
- * COPY [BINARY] FROM/TO
- * [USING DELIMITERS ]
+ * COPY FROM/TO [WITH options]
+ *
+ * BINARY, OIDS, and DELIMITERS kept in old locations
+ * for backward compatibility. 2002-06-18
*
*****************************************************************************/
-CopyStmt: COPY opt_binary qualified_name opt_with_copy copy_dirn copy_file_name copy_delimiter copy_null
+CopyStmt: COPY opt_binary qualified_name opt_oids copy_from
+ copy_file_name copy_delimiter opt_with copy_opt_list
{
CopyStmt *n = makeNode(CopyStmt);
- n->binary = $2;
n->relation = $3;
- n->oids = $4;
- n->direction = $5;
+ n->is_from = $5;
n->filename = $6;
- n->delimiter = $7;
- n->null_print = $8;
+
+ n->options = NIL;
+ /* Concatenate user-supplied flags */
+ if ($2)
+ n->options = lappend(n->options, $2);
+ if ($4)
+ n->options = lappend(n->options, $4);
+ if ($7)
+ n->options = lappend(n->options, $7);
+ if ($9)
+ n->options = nconc(n->options, $9);
$$ = (Node *)n;
}
;
-copy_dirn: TO { $$ = TO; }
- | FROM { $$ = FROM; }
+copy_from:
+ FROM { $$ = TRUE; }
+ | TO { $$ = FALSE; }
;
/*
| STDOUT { $$ = NULL; }
;
-opt_binary: BINARY { $$ = TRUE; }
- | /*EMPTY*/ { $$ = FALSE; }
+
+
+copy_opt_list:
+ copy_opt_list copy_opt_item { $$ = lappend($1, $2); }
+ | /* EMPTY */ { $$ = NIL; }
;
-opt_with_copy:
- WITH OIDS { $$ = TRUE; }
- | /*EMPTY*/ { $$ = FALSE; }
+
+copy_opt_item:
+ BINARY
+ {
+ $$ = makeNode(DefElem);
+ $$->defname = "binary";
+ $$->arg = (Node *)makeInteger(TRUE);
+ }
+ | OIDS
+ {
+ $$ = makeNode(DefElem);
+ $$->defname = "oids";
+ $$->arg = (Node *)makeInteger(TRUE);
+ }
+ | DELIMITER opt_as Sconst
+ {
+ $$ = makeNode(DefElem);
+ $$->defname = "delimiter";
+ $$->arg = (Node *)makeString($3);
+ }
+ | NULL_P opt_as Sconst
+ {
+ $$ = makeNode(DefElem);
+ $$->defname = "null";
+ $$->arg = (Node *)makeString($3);
+ }
+ ;
+
+/* The following exist for backward compatibility */
+
+opt_binary:
+ BINARY
+ {
+ $$ = makeNode(DefElem);
+ $$->defname = "binary";
+ $$->arg = (Node *)makeInteger(TRUE);
+ }
+ | /*EMPTY*/ { $$ = NULL; }
+ ;
+
+opt_oids:
+ WITH OIDS
+ {
+ $$ = makeNode(DefElem);
+ $$->defname = "oids";
+ $$->arg = (Node *)makeInteger(TRUE);
+ }
+ | /*EMPTY*/ { $$ = NULL; }
;
-/*
- * the default copy delimiter is tab but the user can configure it
- */
copy_delimiter:
- opt_using DELIMITERS Sconst { $$ = $3; }
- | /*EMPTY*/ { $$ = "\t"; }
+ /* USING DELIMITERS kept for backward compatibility. 2002-06-15 */
+ opt_using DELIMITERS Sconst
+ {
+ $$ = makeNode(DefElem);
+ $$->defname = "delimiter";
+ $$->arg = (Node *)makeString($3);
+ }
+ | /*EMPTY*/ { $$ = NULL; }
;
-opt_using: USING {}
+opt_using:
+ USING {}
| /*EMPTY*/ {}
;
-copy_null: WITH NULL_P AS Sconst { $$ = $4; }
- | /*EMPTY*/ { $$ = "\\N"; }
- ;
/*****************************************************************************
*
| /* EMPTY */ { $$ = NIL; }
;
-/*
- * createdb_opt_item returns 2-element lists, with the first element
- * being an integer code to indicate which item was specified.
- */
createdb_opt_item:
LOCATION opt_equal Sconst
{
| DEFERRED
| DEFINER
| DELETE_P
+ | DELIMITER
| DELIMITERS
| DOMAIN_P
| DOUBLE
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/parser/keywords.c,v 1.114 2002/06/15 03:00:03 thomas Exp $
+ * $Header: /cvsroot/pgsql/src/backend/parser/keywords.c,v 1.115 2002/06/20 16:00:43 momjian Exp $
*
*-------------------------------------------------------------------------
*/
{"deferred", DEFERRED},
{"definer", DEFINER},
{"delete", DELETE_P},
+ {"delimiter", DELIMITER},
{"delimiters", DELIMITERS},
{"desc", DESC},
{"distinct", DISTINCT},
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/tcop/utility.c,v 1.157 2002/06/18 17:27:58 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/tcop/utility.c,v 1.158 2002/06/20 16:00:43 momjian Exp $
*
*-------------------------------------------------------------------------
*/
{
CopyStmt *stmt = (CopyStmt *) parsetree;
- if (stmt->direction != FROM )
+ if (!stmt->is_from )
SetQuerySnapshot();
- DoCopy(stmt->relation,
- stmt->binary,
- stmt->oids,
- (bool) (stmt->direction == FROM),
- (bool) (stmt->filename == NULL),
-
- /*
- * null filename means copy to/from stdout/stdin, rather
- * than to/from a file.
- */
- stmt->filename,
- stmt->delimiter,
- stmt->null_print);
+ DoCopy(stmt);
}
break;
Notice that there are two consecutive tildes to allow for the fact that this
particular entry doesn't have anything in the Editor field.
You can then perform a
Query as follows:
-COPY psyref FROM '/home/jim/newref.txt' USING DELIMITERS
+COPY psyref FROM '/home/jim/newref.txt' WITH DELIMITER
This will read the records from newref.txt and insert them into the
table psyref . See the PostgreSQL documentation under the headings
" {} "
COPY \[ BINARY \] table \[ WITH OIDS \]
FROM { 'filename' | stdin }
- \[ USING DELIMITERS 'delimiter' \]
+ \[ WITH DELIMITER 'delimiter' \]
COPY \[ BINARY \] table \[ WITH OIDS \]
TO { 'filename' | stdout }
- \[ USING DELIMITERS 'delimiter' \]
+ \[ WITH DELIMITER 'delimiter' \]
" {code} "Inputs" {bold} "
" {} "Usage" {bold} "
The following example copies a table to standard output, using a vertical bar \(\"|\"\) as the field delimiter:
-COPY country TO stdout USING DELIMITERS '|';
+COPY country TO stdout WITH DELIMITER '|';
To copy data from a Unix file into a table \"country\":
COPY country FROM '/usr1/proj/bray/sql/country_data';
The " {} "BINARY" {bold} " keyword will force all data to be stored/read as binary objects rather than as text. It is somewhat faster than the normal copy command, but is not generally portable, and the files \
generated are somewhat larger, although this factor is highly dependent on the data itself. By default, a text copy uses a tab \
-\(\"\\t\"\) character as a delimiter. The delimiter may also be changed to any other single character with the keyword phrase USING DELIMITERS . Characters in data fields which happen to match the delimiter character will be quoted.
+\(\"\\t\"\) character as a delimiter. The delimiter may also be changed to any other single character with the keyword phrase WITH DELIMITER . Characters in data fields which happen to match the delimiter character will be quoted.
You must have select access on any table whose values are read by " {} "COPY" {bold} ", and either insert or update access to a table into which values are being inserted by \
" {} "COPY" {bold} ". The backend also needs appropriate Unix permissions for any file read or written by \
" {} "COPY" {bold} ".
-The keyword phrase " {} "USING DELIMITERS" {bold} " specifies a single character to be used for all delimiters between columns. If multiple characters are specified in the delimiter string, only the first \
-character is used.
+The keyword phrase " {} "WITH DELIMITER" {bold} " specifies a single character to be used for all delimiters between columns.
Tip: Do not confuse " {} "COPY" {bold} " with the psql instruction \\copy. "
if {$PgAcVar(impexp,delimiter)==""} {
set sup ""
} else {
+ # now we use WITH DELIMITER, but keep old syntax for
+ # backward compatibility. 2002-06-15
set sup " USING DELIMITERS '$PgAcVar(impexp,delimiter)'"
}
if {[.pgaw:ImportExport.expbtn cget -text]=="Import"} {
*
* Copyright 2000 by PostgreSQL Global Development Group
*
- * $Header: /cvsroot/pgsql/src/bin/psql/copy.c,v 1.22 2002/04/24 21:00:10 petere Exp $
+ * $Header: /cvsroot/pgsql/src/bin/psql/copy.c,v 1.23 2002/06/20 16:00:44 momjian Exp $
*/
#include "postgres_fe.h"
#include "copy.h"
* parse_slash_copy
* -- parses \copy command line
*
- * Accepted syntax: \copy [binary] table|"table" [with oids] from|to filename|'filename' [ using delimiters ''] [ with null as 'string' ]
+ * Accepted syntax: \copy table|"table" [with oids] from|to filename|'filename' [with ] [ oids ] [ delimiter ''] [ null as 'string' ]
* (binary is not here yet)
*
+ * Old syntax for backward compatibility: (2002-06-19):
+ * \copy table|"table" [with oids] from|to filename|'filename' [ using delimiters ''] [ with null as 'string' ]
+ *
* returns a malloc'ed structure with the options, or NULL on parsing error
*/
error = true;
else
{
+ /* Allows old COPY syntax for backward compatibility 2002-06-19 */
if (strcasecmp(token, "with") == 0)
{
token = strtokx(NULL, " \t\n\r", NULL, '\\', NULL, NULL, pset.encoding);
token = strtokx(NULL, " \t\n\r", NULL, '\\', NULL, NULL, pset.encoding);
if (token)
{
+ /* Allows old COPY syntax for backward compatibility 2002-06-19 */
if (strcasecmp(token, "using") == 0)
{
token = strtokx(NULL, " \t\n\r", NULL, '\\', NULL, NULL, pset.encoding);
- if (!token || strcasecmp(token, "delimiters") != 0)
- error = true;
- else
+ if (token && strcasecmp(token, "delimiters") == 0)
{
token = strtokx(NULL, " \t\n\r", "'", '\\', NULL, NULL, pset.encoding);
if (token)
else
error = true;
}
+ else
+ error = true;
}
+ }
+ }
- if (!error && token)
+ if (!error && token)
+ {
+ if (strcasecmp(token, "with") == 0)
+ {
+ while (!error && (token = strtokx(NULL, " \t\n\r", NULL, '\\', NULL, NULL, pset.encoding)))
{
- if (strcasecmp(token, "with ") == 0)
+ if (strcasecmp(token, "delimiter ") == 0)
{
- token = strtokx(NULL, " \t\n\r", NULL, '\\', NULL, NULL, pset.encoding);
- if (!token || strcasecmp(token, "null") != 0)
+ token = strtokx(NULL, " \t\n\r", "'", '\\', NULL, NULL, pset.encoding);
+ if (token && strcasecmp(token, "as") == 0)
+ token = strtokx(NULL, " \t\n\r", "'", '\\', NULL, NULL, pset.encoding);
+ if (token)
+ result->delim = xstrdup(token);
+ else
error = true;
+ }
+ else if (strcasecmp(token, "null") == 0)
+ {
+ token = strtokx(NULL, " \t\n\r", "'", '\\', NULL, NULL, pset.encoding);
+ if (token && strcasecmp(token, "as") == 0)
+ token = strtokx(NULL, " \t\n\r", "'", '\\', NULL, NULL, pset.encoding);
+ if (token)
+ result->null = xstrdup(token);
else
- {
- token = strtokx(NULL, " \t\n\r", NULL, '\\', NULL, NULL, pset.encoding);
- if (!token || strcasecmp(token, "as") != 0)
- error = true;
- else
- {
- token = strtokx(NULL, " \t\n\r", "'", '\\', NULL, NULL, pset.encoding);
- if (token)
- result->null = xstrdup(token);
- }
- }
+ error = true;
}
- else
- error = true;
+ else error = true;
}
}
+ else error = true;
}
free(line);
appendPQExpBuffer(&query, "BINARY ");
appendPQExpBuffer(&query, "\"%s\" ", options->table);
+ /* Uses old COPY syntax for backward compatibility 2002-06-19 */
if (options->oids)
appendPQExpBuffer(&query, "WITH OIDS ");
appendPQExpBuffer(&query, "TO STDOUT");
+ /* Uses old COPY syntax for backward compatibility 2002-06-19 */
if (options->delim)
appendPQExpBuffer(&query, " USING DELIMITERS '%s'", options->delim);
free_copy_options(options);
return false;
}
-
+
result = PSQLexec(query.data);
termPQExpBuffer(&query);
* Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California
*
- * $Id: copy.h,v 1.17 2002/03/29 19:06:21 tgl Exp $
+ * $Id: copy.h,v 1.18 2002/06/20 16:00:44 momjian Exp $
*
*-------------------------------------------------------------------------
*/
#ifndef COPY_H
#define COPY_H
+#include "nodes/parsenodes.h"
#include "nodes/primnodes.h"
extern int copy_lineno;
-void DoCopy(const RangeVar *relation, bool binary, bool oids,
- bool from, bool pipe,
- char *filename, char *delim, char *null_print);
+void DoCopy(const CopyStmt *stmt);
#endif /* COPY_H */
* Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California
*
- * $Id: dbcommands.h,v 1.22 2002/06/18 17:27:58 momjian Exp $
+ * $Id: dbcommands.h,v 1.23 2002/06/20 16:00:44 momjian Exp $
*
*-------------------------------------------------------------------------
*/
#include
-extern void createdb(CreatedbStmt *stmt);
+extern void createdb(const CreatedbStmt *stmt);
extern void dropdb(const char *dbname);
extern void AlterDatabaseSet(AlterDatabaseSetStmt *stmt);
* Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California
*
- * $Id: parsenodes.h,v 1.180 2002/06/18 17:27:58 momjian Exp $
+ * $Id: parsenodes.h,v 1.181 2002/06/20 16:00:44 momjian Exp $
*
*-------------------------------------------------------------------------
*/
typedef struct CopyStmt
{
NodeTag type;
- bool binary; /* is a binary copy? */
RangeVar *relation; /* the relation to copy */
- bool oids; /* copy oid's? */
- int direction; /* TO or FROM */
+ bool is_from; /* TO or FROM */
char *filename; /* if NULL, use stdin/stdout */
- char *delimiter; /* delimiter character, \t by default */
- char *null_print; /* how to print NULLs, `\N' by default */
+ List *options; /* List of DefElem nodes */
} CopyStmt;
/* ----------------------
/*
* This class provides information about the database as a whole.
*
- * $Id: DatabaseMetaData.java,v 1.46 2002/06/11 02:55:16 barry Exp $
+ * $Id: DatabaseMetaData.java,v 1.47 2002/06/20 16:00:44 momjian Exp $
*
*
Many of the methods here return lists of information in ResultSets. You
* can use the normal ResultSet methods such as getString and getInt to
*/
public String getSQLKeywords() throws SQLException
{
- return "abort,acl,add,aggregate,append,archive,arch_store,backward,binary,change,cluster,copy,database,delimiters,do,extend,explain,forward,heavy,index,inherits,isnull,light,listen,load,merge,nothing,notify,notnull,oids,purge,rename,replace,retrieve,returns,rule,recipe,setof,stdin,stdout,store,vacuum,verbose,version";
+ return "abort,acl,add,aggregate,append,archive,arch_store,backward,binary,change,cluster,copy,database,delimiter,delimiter s,do,extend,explain,forward,heavy,index,inherits,isnull,light,listen,load,merge,nothing,notify,notnull,oids,purge,rename,replace,retrieve,returns,rule,recipe,setof,stdin,stdout,store,vacuum,verbose,version";
}
public String getNumericFunctions() throws SQLException
/*
* This class provides information about the database as a whole.
*
- * $Id: DatabaseMetaData.java,v 1.55 2002/06/11 02:55:16 barry Exp $
+ * $Id: DatabaseMetaData.java,v 1.56 2002/06/20 16:00:44 momjian Exp $
*
*
Many of the methods here return lists of information in ResultSets. You
* can use the normal ResultSet methods such as getString and getInt to
public String getSQLKeywords() throws SQLException
{
if (Driver.logDebug) Driver.debug("getSQLKeyWords");
- return "abort,acl,add,aggregate,append,archive,arch_store,backward,binary,change,cluster,copy,database,delimiters,do,extend,explain,forward,heavy,index,inherits,isnull,light,listen,load,merge,nothing,notify,notnull,oids,purge,rename,replace,retrieve,returns,rule,recipe,setof,stdin,stdout,store,vacuum,verbose,version";
+ return "abort,acl,add,aggregate,append,archive,arch_store,backward,binary,change,cluster,copy,database,delimiter,delimiter s,do,extend,explain,forward,heavy,index,inherits,isnull,light,listen,load,merge,nothing,notify,notnull,oids,purge,rename,replace,retrieve,returns,rule,recipe,setof,stdin,stdout,store,vacuum,verbose,version";
}
public String getNumericFunctions() throws SQLException
-COPY wordlist FROM stdin USING DELIMITERS '|';
+COPY wordlist FROM stdin WITH DELIMITER '|';
AAA |ÄÄÄ
AAAAa |ÄÄÄÄä
BBBB |BBBB
-COPY wordlist FROM stdin USING DELIMITERS '|';
+COPY wordlist FROM stdin WITH DELIMITER '|';
AAA |ÄÄÄ
AAAAa |ÄÄÄÄä
BBBB |BBBB
-COPY usastates FROM stdin USING DELIMITERS '|';
+COPY usastates FROM stdin WITH DELIMITER '|';
AK|Alaska |ÁëÜóêá
WA|Washington |Ãïõüóéíãêôïí
OR|Oregon |Ïñåãêïí
-COPY usastates FROM stdin USING DELIMITERS '|';
+COPY usastates FROM stdin WITH DELIMITER '|';
AK|Alaska |áÌÑÓËÁ
WA|Washington |÷ÁÛÉÎÇÔÏÎ
OR|Oregon |ïÒÅÇÏÎ
-COPY usastates FROM stdin USING DELIMITERS '|';
+COPY usastates FROM stdin WITH DELIMITER '|';
AK|Alaska |Àëÿñêà
WA|Washington |Âàøèíãòîí
OR|Oregon |Îðåãîí
projects / postgresql.git / commitdiff