psql is a terminal-based front-end to PostgreSQL. It enables you to type in queries interactively, issue them to PostgreSQL, and see the query results. Alternatively, input can be from a file. In addition, it provides a number of meta-commands and various shell-like features to facilitate writing scripts and automating a wide variety of tasks.
Print all input lines to standard output as they are read. This is more useful for script processing than interactive mode. This is equivalent to setting the variable ECHO to all.
Switches to unaligned output mode. (The default output mode is otherwise aligned.)
Specifies that psql is to execute one command string, command, and then exit. This is useful in shell scripts. Start-up files (psqlrc and ~/.psqlrc) are ignored with this option.
command must be either a command string that is completely parsable by the server (i.e., it contains no psql-specific features), or a single backslash command. Thus you cannot mix SQL and psql meta-commands with this option. To achieve that, you could pipe the string into psql, like this: echo '\x \\ SELECT * FROM foo;' | psql. (\\ is the separator meta-command.)
If the command string contains multiple SQL commands, they are processed in a single transaction, unless there are explicit BEGIN/COMMIT commands included in the string to divide it into multiple transactions. This is different from the behavior when the same string is fed to psql's standard input.
Specifies the name of the database to connect to. This is equivalent to specifying dbname as the first non-option argument on the command line.
If this parameter contains an = sign, it is treated as a conninfo string. See Section 31.1 for more information.
Copy all SQL commands sent to the server to standard output as well. This is equivalent to setting the variable ECHO to queries.
Echo the actual queries generated by \d and other backslash commands. You can use this to study psql's internal operations. This is equivalent to setting the variable ECHO_HIDDEN from within psql.
Use the file filename as the source of commands instead of reading commands interactively. After the file is processed, psql terminates. This is in many ways equivalent to the internal command \i.
If filename is - (hyphen), then standard input is read.
Using this option is subtly different from writing psql < filename. In general, both will do what you expect, but using -f enables some nice features such as error messages with line numbers. There is also a slight chance that using this option will reduce the start-up overhead. On the other hand, the variant using the shell's input redirection is (in theory) guaranteed to yield exactly the same output you would have received had you entered everything by hand.
Use separator as the field separator for unaligned output. This is equivalent to \pset fieldsep or \f.
Specifies the host name of the machine on which the server is running. If the value begins with a slash, it is used as the directory for the Unix-domain socket.
Turn on HTML tabular output. This is equivalent to \pset format html or the \H command.
List all available databases, then exit. Other non-connection options are ignored. This is similar to the internal command \list.
Write all query output into file filename, in addition to the normal output destination.
Do not use readline for line editing and do not use the history. This can be useful to turn off tab expansion when cutting and pasting.
Put all query output into file filename. This is equivalent to the command \o.
Specifies the TCP port or the local Unix-domain socket file extension on which the server is listening for connections. Defaults to the value of the PGPORT environment variable or, if not set, to the port specified at compile time, usually 5432.
Specifies printing options, in the style of \pset. Note that here you have to separate name and value with an equal sign instead of a space. For example, to set the output format to LaTeX, you could write -P format=latex.
Specifies that psql should do its work quietly. By default, it prints welcome messages and various informational output. If this option is used, none of this happens. This is useful with the -c option. Within psql you can also set the QUIET variable to achieve the same effect.
Use separator as the record separator for unaligned output. This is equivalent to the \pset recordsep command.
Run in single-step mode. That means the user is prompted before each command is sent to the server, with the option to cancel execution as well. Use this to debug scripts.
Runs in single-line mode where a newline terminates an SQL command, as a semicolon does.
Note: This mode is provided for those who insist on it, but you are not necessarily encouraged to use it. In particular, if you mix SQL and meta-commands on a line the order of execution might not always be clear to the inexperienced user.
Turn off printing of column names and result row count footers, etc. This is equivalent to the \t command.
Specifies options to be placed within the
HTML table
tag. See
\pset for details.
Connect to the database as the user username instead of the default. (You must have permission to do so, of course.)
Perform 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.
Print the psql version and exit.
Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as a .pgpass file, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to enter a password.
Note that this option will remain set for the entire session, and so it affects uses of the meta-command \connect as well as the initial connection attempt.
Force psql to prompt for a password before connecting to a database.
This option is never essential, since psql will automatically prompt for a password if the server demands password authentication. However, psql will waste a connection attempt finding out that the server wants a password. In some cases it is worth typing -W to avoid the extra connection attempt.
Note that this option will remain set for the entire session, and so it affects uses of the meta-command \connect as well as the initial connection attempt.
Turn on the expanded table formatting mode. This is equivalent to the \x command.
Do not read the start-up file (neither the system-wide psqlrc file nor the user's ~/.psqlrc file).
When psql executes a script with the -f option, adding this option wraps BEGIN/COMMIT around the script to execute it as a single transaction. This ensures that either all the commands complete successfully, or no changes are applied.
If the script itself uses BEGIN, COMMIT, or ROLLBACK, this option will not have the desired effects. Also, if the script contains any command that cannot be executed inside a transaction block, specifying this option will cause that command (and hence the whole transaction) to fail.
Show help about psql command line arguments, and exit.
psql returns 0 to the shell if it finished normally, 1 if a fatal error of its own occurs (e.g. out of memory, file not found), 2 if the connection to the server went bad and the session was not interactive, and 3 if an error occurred in a script and the variable ON_ERROR_STOP was set.
psql is a regular PostgreSQL client application. In order to connect to a database you need to know the name of your target database, the host name and port number of the server, and what user name you want to connect as. psql can be told about those parameters via command line options, namely -d, -h, -p, and -U respectively. If an argument is found that does not belong to any option it will be interpreted as the database name (or the user name, if the database name is already given). Not all of these options are required; there are useful defaults. If you omit the host name, psql will connect via a Unix-domain socket to a server on the local host, or via TCP/IP to localhost on machines that don't have Unix-domain sockets. The default port number is determined at compile time. Since the database server uses the same default, you will not have to specify the port in most cases. The default user name is your Unix user name, as is the default database name. Note that you cannot just connect to any database under any user name. Your database administrator should have informed you about your access rights.
When the defaults aren't quite right, you can save yourself some typing by setting the environment variables PGDATABASE, PGHOST, PGPORT and/or PGUSER to appropriate values. (For additional environment variables, see Section 31.13.) It is also convenient to have a ~/.pgpass file to avoid regularly having to type in passwords. See Section 31.14 for more information.
An alternative way to specify connection parameters is in a conninfo string, which is used instead of a database name. This mechanism give you very wide control over the connection. For example:
$ psql "service=myservice sslmode=require"
This way you can also use LDAP for connection parameter lookup as described in Section 31.16. See Section 31.1 for more information on all the available connection options.
If the connection could not be made for any reason (e.g., insufficient privileges, server is not running on the targeted host, etc.), psql will return an error and terminate.
In normal operation, psql provides a prompt with the name of the database to which psql is currently connected, followed by the string =>. For example:
$ psql testdb psql (9.0.10) Type "help" for help. testdb=>
At the prompt, the user can type in SQL commands. Ordinarily, input lines are sent to the server when a command-terminating semicolon is reached. An end of line does not terminate a command. Thus commands can be spread over several lines for clarity. If the command was sent and executed without error, the results of the command are displayed on the screen.
Whenever a command is executed, psql also polls for asynchronous notification events generated by LISTEN and NOTIFY.
Anything you enter in psql that begins with an unquoted backslash is a psql meta-command that is processed by psql itself. These commands make psql more useful for administration or scripting. Meta-commands are often called slash or backslash commands.
The format of a psql command is the backslash, followed immediately by a command verb, then any arguments. The arguments are separated from the command verb and each other by any number of whitespace characters.
To include whitespace into an argument you can quote it with a single quote. To include a single quote into such an argument, use two single quotes. Anything contained in single quotes is furthermore subject to C-like substitutions for \n (new line), \t (tab), \digits (octal), and \xdigits (hexadecimal).
If an unquoted argument begins with a colon (:), it is taken as a psql variable and the value of the variable is used as the argument instead. If the variable name is surrounded by single quotes (e.g. :'var'), it will be escaped as an SQL literal and the result will be used as the argument. If the variable name is surrounded by double quotes, it will be escaped as an SQL identifier and the result will be used as the argument.
Arguments that are enclosed in backquotes (`) are taken as a command line that is passed to the shell. The output of the command (with any trailing newline removed) is taken as the argument value. The above escape sequences also apply in backquotes.
Some commands take an SQL identifier (such as a table name) as argument. These arguments follow the syntax rules of SQL: Unquoted letters are forced to lowercase, while double quotes (") protect letters from case conversion and allow incorporation of whitespace into the identifier. Within double quotes, paired double quotes reduce to a single double quote in the resulting name. For example, FOO"BAR"BAZ is interpreted as fooBARbaz, and "A weird"" name" becomes A weird" name.
Parsing for arguments stops at the end of the line, or when another unquoted backslash is found. An unquoted backslash is taken as the beginning of a new meta-command. The special sequence \\ (two backslashes) marks the end of arguments and continues parsing SQL commands, if any. That way SQL and psql commands can be freely mixed on a line. But in any case, the arguments of a meta-command cannot continue beyond the end of the line.
The following meta-commands are defined:
If the current table output format is unaligned, it is switched to aligned. If it is not unaligned, it is set to unaligned. This command is kept for backwards compatibility. See \pset for a more general solution.
Changes the current working directory to directory. Without argument, changes to the current user's home directory.
Tip: To print your current working directory, use \! pwd.
Sets the title of any tables being printed as the result of a query or unset any such title. This command is equivalent to \pset title title. (The name of this command derives from "caption", as it was previously only used to set the caption in an HTML table.)
Establishes a new connection to a PostgreSQL server. If the new connection is successfully made, the previous connection is closed. If any of dbname, username, host or port are omitted or specified as -, the value of that parameter from the previous connection is used. If there is no previous connection, the libpq default for the parameter's value is used.
If the connection attempt failed (wrong user name, access denied, etc.), the previous connection will only be kept if psql is in interactive mode. When executing a non-interactive script, processing will immediately stop with an error. This distinction was chosen as a user convenience against typos on the one hand, and a safety mechanism that scripts are not accidentally acting on the wrong database on the other hand.
Performs a frontend (client) copy. This is an operation that runs an SQL COPY command, but instead of the server reading or writing the specified file, psql reads or writes the file and routes the data between the server and the local file system. This means that file accessibility and privileges are those of the local user, not the server, and no SQL superuser privileges are required.
The syntax of the command is similar to that of the SQL COPY command. Note that, because of this, special parsing rules apply to the \copy command. In particular, the variable substitution rules and backslash escapes do not apply.
\copy ... from stdin | to stdout reads/writes based on the command input and output respectively. All rows are read from the same source that issued the command, continuing until \. is read or the stream reaches EOF. Output is sent to the same place as command output. To read/write from psql's standard input or output, use pstdin or pstdout. This option is useful for populating tables in-line within a SQL script file.
Tip: This operation is not as efficient as the SQL COPY command because all data must pass through the client/server connection. For large amounts of data the SQL command might be preferable.
Shows the copyright and distribution terms of PostgreSQL.
For each relation (table, view, index, or sequence) matching the pattern, show all columns, their types, the tablespace (if not the default) and any special attributes such as NOT NULL or defaults.  ("Matching the pattern" is defined in Patterns below.)
The command form \d+ is identical, except that more information is displayed: any comments associated with the columns of the table are shown, as is the presence of OIDs in the table, and the view definition if the relation is a view.
By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects.
Note: If \d is used without a pattern argument, it is equivalent to \dtvs which will show a list of all visible tables, views, and sequences. This is purely a convenience measure.
Lists aggregate functions, together with their return type and the data types they operate on. If pattern is specified, only aggregates whose names match the pattern are shown. By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects.
Lists tablespaces. If pattern is specified, only tablespaces whose names match the pattern are shown. If + is appended to the command name, each object is listed with its associated permissions.
Lists conversions between character-set encodings. If pattern is specified, only conversions whose names match the pattern are listed. By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects.
Lists type casts. If pattern is specified, only casts whose source or target types match the pattern are listed.
Shows the descriptions of objects matching the pattern, or of all visible objects if no argument is given. But in either case, only objects that have a description are listed. By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects. "Object" covers aggregates, functions, operators, types, relations (tables, views, indexes, sequences), large objects, rules, and triggers. For example:
=> \dd version Object descriptions Schema | Name | Object | Description ------------+---------+----------+--------------------------- pg_catalog | version | function | PostgreSQL version string (1 row)
Descriptions for objects can be created with the COMMENT SQL command.
Lists default access privilege settings. An entry is shown for each role (and schema, if applicable) for which the default privilege settings have been changed from the built-in defaults. If pattern is specified, only entries whose role name or schema name matches the pattern are listed.
The ALTER DEFAULT PRIVILEGES command is used to set default access privileges. The meaning of the privilege display is explained under GRANT.
Lists domains. If pattern is specified, only domains whose names match the pattern are shown. By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects.
Lists foreign servers (mnemonic: "external servers"). If pattern is specified, only those servers whose name matches the pattern are listed. If the form \des+ is used, a full description of each server is shown, including the server's ACL, type, version, and options.
Lists user mappings (mnemonic: "external users"). If pattern is specified, only those mappings whose user names match the pattern are listed. If the form \deu+ is used, additional information about each mapping is shown.
| Caution |
\deu+ might also display the user name and password of the remote user, so care should be taken not to disclose them. |
Lists foreign-data wrappers (mnemonic: "external wrappers"). If pattern is specified, only those foreign-data wrappers whose name matches the pattern are listed. If the form \dew+ is used, the ACL and options of the foreign-data wrapper are also shown.
Lists functions, together with their arguments, return types, and function types, which are classified as "agg" (aggregate), "normal", "trigger", or "window". To display only functions of specific type(s), add the corresponding letters a, n, t, or w to the command. If pattern is specified, only functions whose names match the pattern are shown. If the form \df+ is used, additional information about each function, including volatility, language, source code and description, is shown. By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects.
Tip: To look up functions taking arguments or returning values of a specific type, use your pager's search capability to scroll through the \df output.
Lists text search configurations. If pattern is specified, only configurations whose names match the pattern are shown. If the form \dF+ is used, a full description of each configuration is shown, including the underlying text search parser and the dictionary list for each parser token type.
Lists text search dictionaries. If pattern is specified, only dictionaries whose names match the pattern are shown. If the form \dFd+ is used, additional information is shown about each selected dictionary, including the underlying text search template and the option values.
Lists text search parsers. If pattern is specified, only parsers whose names match the pattern are shown. If the form \dFp+ is used, a full description of each parser is shown, including the underlying functions and the list of recognized token types.
Lists text search templates. If pattern is specified, only templates whose names match the pattern are shown. If the form \dFt+ is used, additional information is shown about each template, including the underlying function names.
Lists database roles. If pattern is specified, only those roles whose names match the pattern are listed. (This command is now effectively the same as \du). If the form \dg+ is used, additional information is shown about each role, including the comment for each role.
In this group of commands, the letters i, s, t, and v stand for index, sequence, table, and view, respectively. You can specify any or all of these letters, in any order, to obtain a listing of objects of these types. For example, \dit lists indexes and tables. If + is appended to the command name, each object is listed with its physical size on disk and its associated description, if any. If pattern is specified, only objects whose names match the pattern are listed. By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects.
This is an alias for \lo_list, which shows a list of large objects.
Lists schemas (namespaces). If pattern is specified, only schemas whose names match the pattern are listed. Non-local temporary schemas are suppressed. If + is appended to the command name, each object is listed with its associated permissions and description, if any.
Lists operators with their operand and return types. If pattern is specified, only operators whose names match the pattern are listed. By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects.
Lists tables, views and sequences with their associated access privileges. If pattern is specified, only tables, views and sequences whose names match the pattern are listed.
The GRANT and REVOKE commands are used to set access privileges. The meaning of the privilege display is explained under GRANT.
Lists defined configuration settings. These settings can be role-specific, database-specific, or both. role-pattern and database-pattern are used to select specific roles and databases to list, respectively. If omitted, or if * is specified, all settings are listed, including those not role-specific or database-specific, respectively.
The ALTER ROLE and ALTER DATABASE commands are used to define per-role and per-database configuration settings.
Lists data types. If pattern is specified, only types whose names match the pattern are listed. If + is appended to the command name, each type is listed with its internal name and size, as well as its allowed values if it is an enum type. By default, only user-created objects are shown; supply a pattern or the S modifier to include system objects.
Lists database roles. If pattern is specified, only those roles whose names match the pattern are listed. If the form \du+ is used, additional information is shown about each role, including the comment for each role.
If filename is specified, the file is edited; after the editor exits, its content is copied back to the query buffer. If no argument is given, the current query buffer is copied to a temporary file which is then edited in the same fashion.
The new query buffer is then re-parsed according to the normal rules of psql, where the whole buffer is treated as a single line. (Thus you cannot make scripts this way. Use \i for that.) This means also that if the query ends with (or rather contains) a semicolon, it is immediately executed. In other cases it will merely wait in the query buffer.
Tip: psql searches the environment variables PSQL_EDITOR, EDITOR, and VISUAL (in that order) for an editor to use. If all of them are unset, vi is used on Unix systems, notepad.exe on Windows systems.
This command fetches and edits the definition of the named function, in the form of a CREATE OR REPLACE FUNCTION command. Editing is done in the same way as for \e. After the editor exits, the updated command waits in the query buffer; type semicolon or \g to send it, or \r to cancel.
The target function can be specified by name alone, or by name and arguments, for example foo(integer, text). The argument types must be given if there is more than one function of the same name.
If no function is specified, a blank CREATE FUNCTION template is presented for editing.
Prints the arguments to the standard output, separated by one space and followed by a newline. This can be useful to intersperse information in the output of scripts. For example:
=> \echo `date` Tue Oct 26 21:40:57 CEST 1999
If the first argument is an unquoted -n the trailing newline is not written.
Tip: If you use the \o command to redirect your query output you might wish to use \qecho instead of this command.
Sets the client character set encoding. Without an argument, this command shows the current encoding.
Sets the field separator for unaligned query output. The default is the vertical bar (|). See also \pset for a generic way of setting output options.
Sends the current query input buffer to the server and optionally stores the query's output in filename or pipes the output into a separate Unix shell executing command. A bare \g is virtually equivalent to a semicolon. A \g with argument is a "one-shot" alternative to the \o command.
Gives syntax help on the specified SQL command. If command is not specified, then psql will list all the commands for which syntax help is available. If command is an asterisk (*), then syntax help on all SQL commands is shown.
Note: To simplify typing, commands that consists of several words do not have to be quoted. Thus it is fine to type \help alter table.
Turns on HTML query output format. If the HTML format is already on, it is switched back to the default aligned text format. This command is for compatibility and convenience, but see \pset about setting other output options.
Reads input from the file filename and executes it as though it had been typed on the keyboard.
Note: If you want to see the lines on the screen as they are read you must set the variable ECHO to all.
List the names, owners, character set encodings, and access privileges of all the databases in the server. If + is appended to the command name, database sizes, default tablespaces, and descriptions are also displayed. (Size information is only available for databases that the current user can connect to.)
Reads the large object with OID loid from the database and
writes it to filename. Note that this is
subtly different from the server function
lo_export
, which acts with the permissions
of the user that the database server runs as and on the server's
file system.
Tip: Use \lo_list to find out the large object's OID.
Stores the file into a PostgreSQL large object. Optionally, it associates the given comment with the object. Example:
foo=> \lo_import '/home/peter/pictures/photo.xcf' 'a picture of me' lo_import 152801
The response indicates that the large object received object ID 152801, which can be used to access the newly-created large object in the future. For the sake of readability, it is recommended to always associate a human-readable comment with every object. Both OIDs and comments can be viewed with the \lo_list command.
Note that this command is subtly different from the server-side
lo_import
because it acts as the local user
on the local file system, rather than the server's user and file
system.
Shows a list of all PostgreSQL large objects currently stored in the database, along with any comments provided for them.
Deletes the large object with OID loid from the database.
Tip: Use \lo_list to find out the large object's OID.
Saves future query results to the file filename or pipes future results into a separate Unix shell to execute command. If no arguments are specified, the query output will be reset to the standard output.
"Query results" includes all tables, command responses, and notices obtained from the database server, as well as output of various backslash commands that query the database (such as \d), but not error messages.
Tip: To intersperse text output in between query results, use \qecho.
Print the current query buffer to the standard output.
Changes the password of the specified user (by default, the current user). This command prompts for the new password, encrypts it, and sends it to the server as an ALTER ROLE command. This makes sure that the new password does not appear in cleartext in the command history, the server log, or elsewhere.
Prompts the user to set variable name. An optional prompt, text, can be specified. (For multiword prompts, use single quotes.)
By default, \prompt uses the terminal for input and output. However, if the -f command line switch is used, \prompt uses standard input and standard output.
This command sets options affecting the output of query result tables. option indicates which option is to be set. The semantics of value vary depending on the selected option. For some options, omitting value causes the option to be toggled or unset, as described under the particular option. If no such behavior is mentioned, then omitting value just results in the current setting being displayed.
Adjustable printing options are:
Sets the output format to one of unaligned, aligned, wrapped, html, latex, or troff-ms. Unique abbreviations are allowed. (That would mean one letter is enough.)
unaligned format writes all columns of a row on one line, separated by the currently active field separator. This is useful for creating output that might be intended to be read in by other programs (for example, tab-separated or comma-separated format).
aligned format is the standard, human-readable, nicely formatted text output; this is the default.
wrapped format is like aligned but wraps wide data values across lines to make the output fit in the target column width. The target width is determined as described under the columns option. Note that psql will not attempt to wrap column header titles; therefore, wrapped format behaves the same as aligned if the total width needed for column headers exceeds the target.
The html, latex, and troff-ms formats put out tables that are intended to be included in documents using the respective mark-up language. They are not complete documents! (This might not be so dramatic in HTML, but in LaTeX you must have a complete document wrapper.)
Sets the target width for the wrapped format, and also the width limit for determining whether output is wide enough to require the pager. Zero (the default) causes the target width to be controlled by the environment variable COLUMNS, or the detected screen width if COLUMNS is not set. In addition, if columns is zero then the wrapped format only affects screen output. If columns is nonzero then file and pipe output is wrapped to that width as well.
The value must be a number. In general, the higher the number the more borders and lines the tables will have, but this depends on the particular format. In HTML format, this will translate directly into the border=... attribute; in the other formats only values 0 (no border), 1 (internal dividing lines), and 2 (table frame) make sense.
Sets the border line drawing style to one of ascii, old-ascii or unicode. Unique abbreviations are allowed. (That would mean one letter is enough.) The default setting is ascii. This option only affects the aligned and wrapped output formats.
ascii style uses plain ASCII characters. Newlines in data are shown using a + symbol in the right-hand margin. When the wrapped format wraps data from one line to the next without a newline character, a dot (.) is shown in the right-hand margin of the first line, and again in the left-hand margin of the following line.
old-ascii style uses plain ASCII characters, using the formatting style used in PostgreSQL 8.4 and earlier. Newlines in data are shown using a : symbol in place of the left-hand column separator. When the data is wrapped from one line to the next without a newline character, a ; symbol is used in place of the left-hand column separator.
unicode style uses Unicode box-drawing characters. Newlines in data are shown using a carriage return symbol in the right-hand margin. When the data is wrapped from one line to the next without a newline character, an ellipsis symbol is shown in the right-hand margin of the first line, and again in the left-hand margin of the following line.
When the border setting is greater than zero, this option also determines the characters with which the border lines are drawn. Plain ASCII characters work everywhere, but Unicode characters look nicer on displays that recognize them.
If value is specified it must be either on or off which will enable or disable expanded mode. If value is omitted the command toggles between regular and expanded mode. When expanded mode is enabled, query results are displayed in two columns, with the column name on the left and the data on the right. This mode is useful if the data wouldn't fit on the screen in the normal "horizontal" mode.
Sets the string to be printed in place of a null value. The default is to print nothing, which can easily be mistaken for an empty string. For example, one might prefer \pset null '(null)'.
Specifies the field separator to be used in unaligned output format. That way one can create, for example, tab- or comma-separated output, which other programs might prefer. To set a tab as field separator, type \pset fieldsep '\t'. The default field separator is '|' (a vertical bar).
If value is specified it must be either on or off which will enable or disable display of the table footer (the (n rows) count). If value is omitted the command toggles footer display on or off.
If value is specified it must be either on or off which will enable or disable display of a locale-specific character to separate groups of digits to the left of the decimal marker. If value is omitted the command toggles between regular and locale-specific numeric output.
Specifies the record (line) separator to use in unaligned output format. The default is a newline character.
If value is specified it must be either on or off which will enable or disable tuples-only mode. If value is omitted the command toggles between regular and tuples-only output. Regular output includes extra information such as column headers, titles, and various footers. In tuples-only mode, only actual table data is shown.
Sets the table title for any subsequently printed tables. This can be used to give your output descriptive tags. If no value is given, the title is unset.
Specifies attributes to be placed inside the
HTML table
tag in
html output format. This
could for example be cellpadding or
bgcolor. Note that you probably don't want
to specify border here, as that is already
taken care of by \pset border.
If no
value is given,
the table attributes are unset.
Controls use of a pager program for query and psql help output. If the environment variable PAGER is set, the output is piped to the specified program. Otherwise a platform-dependent default (such as more) is used.
When the pager option is off, the pager program is not used. When the pager option is on, the pager is used when appropriate, i.e., when the output is to a terminal and will not fit on the screen. The pager option can also be set to always, which causes the pager to be used for all terminal output regardless of whether it fits on the screen. \pset pager without a value toggles pager use on and off.
Illustrations of how these different formats look can be seen in the Examples section.
Tip: There are various shortcut commands for \pset. See \a, \C, \H, \t, \T, and \x.
Note: It is an error to call \pset without any arguments. In the future this case might show the current status of all printing options.
Quits the psql program. In a script file, only execution of that script is terminated.
This command is identical to \echo except that the output will be written to the query output channel, as set by \o.
Resets (clears) the query buffer.
Print or save the command line history to filename. If filename is omitted, the history is written to the standard output. This option is only available if psql is configured to use the GNU Readline library.
Sets the internal variable name to value or, if more than one value is given, to the concatenation of all of them. If no second argument is given, the variable is just set with no value. To unset a variable, use the \unset command.
Valid variable names can contain characters, digits, and underscores. See the section Variables below for details. Variable names are case-sensitive.
Although you are welcome to set any variable to anything you want, psql treats several variables as special. They are documented in the section about variables.
Note: This command is totally separate from the SQL command SET.
Toggles the display of output column name headings and row count footer. This command is equivalent to \pset tuples_only and is provided for convenience.
Specifies attributes to be placed within the
table
tag in HTML
output format. This command is equivalent to \pset
tableattr table_options.
Without parameter, toggles a display of how long each SQL statement takes, in milliseconds. With parameter, sets same.
Outputs the current query buffer to the file filename or pipes it to the Unix command command.
Toggles expanded table formatting mode. As such it is equivalent to \pset expanded.
Lists tables, views and sequences with their associated access privileges. If a pattern is specified, only tables, views and sequences whose names match the pattern are listed.
This is an alias for \dp ("display privileges").
Escapes to a separate Unix shell or executes the Unix command command. The arguments are not further interpreted; the shell will see them as-is.
Shows help information about the backslash commands.
The various \d commands accept a pattern parameter to specify the object name(s) to be displayed. In the simplest case, a pattern is just the exact name of the object. The characters within a pattern are normally folded to lower case, just as in SQL names; for example, \dt FOO will display the table named foo. As in SQL names, placing double quotes around a pattern stops folding to lower case. Should you need to include an actual double quote character in a pattern, write it as a pair of double quotes within a double-quote sequence; again this is in accord with the rules for SQL quoted identifiers. For example, \dt "FOO""BAR" will display the table named FOO"BAR (not foo"bar). Unlike the normal rules for SQL names, you can put double quotes around just part of a pattern, for instance \dt FOO"FOO"BAR will display the table named fooFOObar.
Whenever the pattern parameter is omitted completely, the \d commands display all objects that are visible in the current schema search path — this is equivalent to using * as the pattern. (An object is said to be visible if its containing schema is in the search path and no object of the same kind and name appears earlier in the search path. This is equivalent to the statement that the object can be referenced by name without explicit schema qualification.) To see all objects in the database regardless of visibility, use *.* as the pattern.
Within a pattern, * matches any sequence of characters (including no characters) and ? matches any single character. (This notation is comparable to Unix shell file name patterns.) For example, \dt int* displays tables whose names begin with int. But within double quotes, * and ? lose these special meanings and are just matched literally.
A pattern that contains a dot (.) is interpreted as a schema name pattern followed by an object name pattern. For example, \dt foo*.*bar* displays all tables whose table name includes bar that are in schemas whose schema name starts with foo. When no dot appears, then the pattern matches only objects that are visible in the current schema search path. Again, a dot within double quotes loses its special meaning and is matched literally.
Advanced users can use regular-expression notations such as character classes, for example [0-9] to match any digit. All regular expression special characters work as specified in Section 9.7.3, except for . which is taken as a separator as mentioned above, * which is translated to the regular-expression notation .*, ? which is translated to ., and $ which is matched literally. You can emulate these pattern characters at need by writing ? for ., (R+|) for R*, or (R|) for R?. $ is not needed as a regular-expression character since the pattern must match the whole name, unlike the usual interpretation of regular expressions (in other words, $ is automatically appended to your pattern). Write * at the beginning and/or end if you don't wish the pattern to be anchored. Note that within double quotes, all regular expression special characters lose their special meanings and are matched literally. Also, the regular expression special characters are matched literally in operator name patterns (i.e., the argument of \do).
psql provides variable substitution features similar to common Unix command shells. 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:
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:
testdb=> \echo :foo bar
Note: 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.
If you call \set without a second argument, the variable is set, with an empty string as 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 these 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 that 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 letters (and possibly numbers and underscores). To ensure maximum compatibility in the future, avoid using such variable names for your own purposes. A list of all specially treated variables follows.
When on (the default), each SQL command is automatically committed upon successful completion. To postpone commit in this mode, you must enter a BEGIN or START TRANSACTION SQL command. When off or unset, SQL commands are not committed until you explicitly issue COMMIT or END. The autocommit-off mode works by issuing an implicit BEGIN for you, just before any command that is not already in a transaction block and is not itself a BEGIN or other transaction-control command, nor a command that cannot be executed inside a transaction block (such as VACUUM).
Note: In autocommit-off mode, you must explicitly abandon any failed transaction by entering ABORT or ROLLBACK. Also keep in mind that if you exit the session without committing, your work will be lost.
Note: The autocommit-on mode is PostgreSQL's traditional behavior, but autocommit-off is closer to the SQL spec. If you prefer autocommit-off, you might wish to set it in the system-wide psqlrc file or your ~/.psqlrc file.
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.
If set to all, all lines entered from the keyboard or from a script are written to the standard output before they are parsed or executed. To select this behavior on program start-up, use the switch -a. If set to queries, psql merely prints all queries as they are sent to the server. The switch for this is -e.
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. (To select this behavior on program start-up, use the switch -E.) If you set the variable to the value noexec, the queries are just shown but are not actually sent to the server and executed.
The current client character set encoding.
If this variable is set to an integer value > 0, the results of SELECT queries are fetched and displayed in groups of that many rows, rather than the default behavior of collecting the entire result set before display. Therefore only a limited amount of memory is used, regardless of the size of the result set. Settings of 100 to 1000 are commonly used when enabling this feature. Keep in mind that when using this feature, a query might fail after having already displayed some rows.
Tip: Although you can use any output format with this feature, the default aligned format tends to look bad because each group of FETCH_COUNT rows will be formatted separately, leading to varying column widths across the row groups. The other output formats work better.
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.
Note: This feature was shamelessly plagiarized from Bash.
The file name that will be used to store the history list. The default value is ~/.psql_history. For example, putting:
\set HISTFILE ~/.psql_history- :DBNAME
in ~/.psqlrc will cause psql to maintain a separate history for each database.
Note: This feature was shamelessly plagiarized from Bash.
The number of commands to store in the command history. The default value is 500.
Note: This feature was shamelessly plagiarized from Bash.
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.
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.
Note: This feature was shamelessly plagiarized from Bash.
The value of the last affected OID, as returned from an INSERT or \lo_import command. This variable is only guaranteed to be valid until after the result of the next SQL command has been displayed.
When on, if a statement in a transaction block generates an error, the error is ignored and the transaction continues. When interactive, such errors are only ignored in interactive sessions, and not when reading script files. When off (the default), a statement in a transaction block that generates an error aborts the entire transaction. The on_error_rollback-on mode works by issuing an implicit SAVEPOINT for you, just before each command that is in a transaction block, and rolls back to the savepoint on error.
By default, if non-interactive scripts encounter an error, such as a malformed SQL command 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).
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.
These specify what the prompts psql issues should look like. See Prompting below.
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 -S.
This variable is equivalent to the command line option -s.
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.
This variable can be set to the values default, verbose, or terse to control the verbosity of error reports.
An additional useful feature of psql variables is that you can substitute ("interpolate") them into regular SQL statements. psql provides special facilities for ensuring that values used as SQL literals and identifiers are properly escaped. The syntax for interpolating a value without any special escaping 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. Note that this may be unsafe: 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.
When a value is to be used as an SQL literal or identifier, it is safest to arrange for it to be escaped. To escape the value of a variable as an SQL literal, write a colon followed by the variable name in single quotes. To escape the value an SQL identifier, write a colon followed by the variable name in double quotes. The previous example would be more safely written this way:
testdb=> \set foo 'my_table' testdb=> SELECT * FROM :"foo";
Variable interpolation will not be performed into quoted SQL entities.
One possible use of this mechanism is to copy the contents of a file into a table column. 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');
(Note that this still won't work if my_file.txt contains NUL bytes. psql does not support embedded NUL bytes in variable values.)
Since colons can legally appear in SQL commands, an apparent attempt at interpolation (such as :name, :'name', or :"name") is not changed unless the named variable is currently set. In any case, you can escape a colon with a backslash to protect it from substitution. (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. The colon syntax for escaping a variable's value as an SQL literal or identifier is a psql extension.)
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 command. Prompt 2 is issued when more input is expected during command input because the command 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 row values on the terminal.
The value of the selected 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 location.
The host name of the database server, truncated at the first dot, or [local] if the connection is over a Unix domain socket.
The port number at which the database server is listening.
The database session user name. (The expansion of this value might change during a database session as the result of the command SET SESSION AUTHORIZATION.)
The name of the current database.
Like %/, but the output is ~ (tilde) if the database is your default database.
If the session user is a database superuser, then a #, otherwise a >. (The expansion of this value might change during a database session as the result of the command SET SESSION AUTHORIZATION.)
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, a double quote, or a dollar sign, depending on whether psql expects more input because the command wasn't terminated yet, because you are inside a /* ... */ comment, or because you are inside a quoted or dollar-escaped string. In prompt 3 the sequence doesn't produce anything.
Transaction status: an empty string when not in a transaction block, or * when in a transaction block, or ! when in a failed transaction block, or ? when the transaction state is indeterminate (for example, because there is no connection).
The character with the indicated octal code is substituted.
The value of the psql variable name. See the section Variables for details.
The output of command, similar to ordinary "back-tick" substitution.
Prompts can contain terminal control characters which, for example, change the color, background, or style of the prompt text, or change the title of the terminal window. In order for the line editing features of Readline to work properly, these non-printing control characters must be designated as invisible by surrounding them with %[ and %]. Multiple pairs of these can occur within the prompt. For example:
testdb=> \set PROMPT1 '%[%033[1;33;40m%]%n@%/%R%[%033[0m%]%# '
results in a boldfaced (1;) yellow-on-black (33;40) prompt on VT100-compatible, color-capable terminals.
To insert a percent sign into your prompt, write %%. The default prompts are '%/%R%# ' for prompts 1 and 2, and '>> ' for prompt 3.
Note: This feature was shamelessly plagiarized from tcsh.
psql supports the Readline library for convenient line editing and retrieval. The command history is automatically saved when psql exits and is reloaded when psql starts up. Tab-completion is also supported, although the completion logic makes no claim to be an SQL parser. If for some reason you do not like the tab completion, you can turn it 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.)
If \pset columns is zero, controls the width for the wrapped format and width for determining if wide output requires the pager.
If the query results do not fit on the screen, they are piped through this command. Typical values are more or less. The default is platform-dependent. The use of the pager can be disabled by using the \pset command.
Default connection parameters (see Section 31.13).
Editor used by the \e command. The variables are examined in the order listed; the first that is set is used.
Command executed by the \! command.
Directory for storing temporary files. The default is /tmp.
This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see Section 31.13).
Unless it is passed an -X or -c option, psql attempts to read and execute commands from the system-wide psqlrc file and the user's ~/.psqlrc file before starting up. (On Windows, the user's startup file is named %APPDATA%\postgresql\psqlrc.conf.) See PREFIX/share/psqlrc.sample for information on setting up the system-wide file. It could be used to set up the client or the server to taste (using the \set and SET commands).
Both the system-wide psqlrc file and the user's ~/.psqlrc file can be made version-specific by appending a dash and the PostgreSQL release number, for example ~/.psqlrc-9.0.10. A matching version-specific file will be read in preference to a non-version-specific file.
The command-line history is stored in the file ~/.psql_history, or %APPDATA%\postgresql\psql_history on Windows.
In an earlier life psql allowed the first argument of a single-letter backslash command to start directly after the command, without intervening whitespace. As of PostgreSQL 8.4 this is no longer allowed.
psql is only guaranteed to work 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. Backslash commands are particularly likely to fail if the server is of a newer version than psql itself. However, backslash commands of the \d family should work with servers of versions back to 7.4, though not necessarily with servers newer than psql itself.
psql is built as a "console application". Since the Windows console windows use a different encoding than the rest of the system, you must take special care when using 8-bit characters within psql. If psql detects a problematic console code page, it will warn you at startup. To change the console code page, two things are necessary:
Set the code page by entering cmd.exe /c chcp 1252. (1252 is a code page that is appropriate for German; replace it with your value.) If you are using Cygwin, you can put this command in /etc/profile.
Set the console font to Lucida Console, because the raster font does not work with the ANSI code page.
The first example shows how to spread a command over several lines of input. Notice the changing prompt:
testdb=> CREATE TABLE my_table ( testdb(> first integer not null default 0, testdb(> second text) testdb-> ; CREATE TABLE
Now look at the table definition again:
testdb=> \d my_table Table "my_table" Attribute | Type | Modifier -----------+---------+-------------------- first | integer | not null default 0 second | text |
Now we change the prompt to something more interesting:
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:
peter@localhost testdb=> SELECT * FROM my_table; first | second -------+-------- 1 | one 2 | two 3 | three 4 | four (4 rows)
You can display tables in different ways by using the \pset command:
peter@localhost testdb=> \pset border 2 Border style is 2. peter@localhost testdb=> SELECT * FROM my_table; +-------+--------+ | first | second | +-------+--------+ | 1 | one | | 2 | two | | 3 | three | | 4 | four | +-------+--------+ (4 rows) peter@localhost testdb=> \pset border 0 Border style is 0. peter@localhost testdb=> SELECT * FROM my_table; first second ----- ------ 1 one 2 two 3 three 4 four (4 rows) peter@localhost testdb=> \pset border 1 Border style is 1. peter@localhost testdb=> \pset format unaligned Output format is unaligned. peter@localhost testdb=> \pset fieldsep "," Field separator is ",". peter@localhost testdb=> \pset tuples_only Showing only tuples. peter@localhost testdb=> SELECT second, first FROM my_table; one,1 two,2 three,3 four,4
Alternatively, use the short commands:
peter@localhost testdb=> \a \t \x Output format is aligned. Tuples only is off. Expanded display is on. peter@localhost testdb=> SELECT * FROM my_table; -[ RECORD 1 ]- first | 1 second | one -[ RECORD 2 ]- first | 2 second | two -[ RECORD 3 ]- first | 3 second | three -[ RECORD 4 ]- first | 4 second | four


Free your fitness from yourself.
Earn insurance discounts!
A guide to Fitness Tracker spoofing
About

Is your job preventing you from qualifying for health insurance discounts?
Do you have little time for exercise or limited access to sports facilities?
Are you are unable to afford active adventure holidays?
Or maybe you just want to keep your personal data private without having to pay higher insurance premiums for the privilege?
Fit Bit Spoofing provides a solution. This research project investigates several DIY Fitbit spoofing techniques enabling you to create walking datasets to qualify you for all the benefits of a high exercise lifestyle without actually having to share your personal data with your insurance company.
Our team of experts have conducted an in-depth FitBit Audit to understand how the Fitbit interprets data.
With these simple techniques using everyday devices from your home, we show you how to spoof your walking dataset so that you can qualify for the best discounts.
These techniques can also be used to obsficate your actual behaviors to help you to keep your privacy intact.
METRONOME SPOOF

HEAVY LOCK
METRONOME
PAPER CLIP
PENDULUM SPOOF

ROPE / STRING
WOOD (OPTIONAL)
DRILL SPOOF

DRILL
C-CLAMP
BICYCLE WHEEL SPOOF

BICYCLE
PAPER CLIP (OPTIONAL)
Contact
We'd love to hear of your Fitbit Spoofing techniques. Post them to our team: #unfitbits


Contains all of the interfaces for describing and painting vector graphics as Java objects. Graphical objects are composed into tree structures to represent part-whole hierarchies (Composite design pattern).


WEATHER OUTLOOK
Current Location
Current Conditions
Temperature
Humidity
Wind Speed
UV Index
5 DAY OUTLOOK
Temperature
Humidity
Description
Wind Speed


{% extends '_base.html' %} {% block title %}Change Your Password?{% endblock %} {% block content %}
Please enter your old password, for security's sake, and then enter your new password twice so we can verify you typed it in correctly.


| Total Weight | 11% | |
| Sub-Weightages | ||
| Highways/Motorways | 3.1500% | 30% |
| In KMs | ||
| Within 2 | 100% | 3.150% |
| 2-5 | 75% | 2.36250% |
| 5-8 | 50% | 1.5750% |
| 8-10 | 25% | 0.78750% |
| above 10 | 0% | 0.0000% |
| Total | ||
| Railroad/Station | 1.5750% | 15% |
| within 5 KMs | 100% | 1.575% |
| 5-15 | 75% | 1.18125% |
| 15-30 | 50% | 0.7875% |
| 30-45 | 25% | 0.39375% |
| above 45 | 0% | 0.0000% |
| Total | ||
| Airport | 1.050% | 10% |
| Commercial/Logistics | ||
| within 25 | 100% | 1.050% |
| 25-40 | 75% | 0.78750% |
| 40-60 | 50% | 0.5250% |
| 60-100 | 25% | 0.26250% |
| above 100 | 0% | 0.0000% |
| Total | ||
| Trucking Stations/Interchanges | 1.050% | 10% |
| 0-5 | 100% | 1.050% |
| 5-8 | 75% | 0.78750% |
| 8-15 | 50% | 0.5250% |
| 15-25 | 25% | 0.26250% |
| above 25 | 0% | 0.0000% |
| Total | ||
| Shipping Cost/DryPort | 1.5750% | 15% |
| within 20 | 100% | 1.5750% |
| 20-40 | 75% | 1.181250% |
| 40-60 | 50% | 0.78750% |
| 60-100 | 25% | 0.393750% |
| above 100 | 0% | 0.0000% |
| Total | ||
| Warehouse/Storage(in Dist) | 1.0500% | 10% |
| Highly available | 100% | 1.050% |
| Medium Available | 75% | 0.78750% |
| Available | 50% | 0.5250% |
| Low Available | 25% | 0.26250% |
| No Available | 0% | 0.0000% |
| Total | ||
| Transport Time | 1.050% | 10% |
| Carpted Road/Double with limited traffic | 100% | 1.050% |
| Carpted with Heavy Traffic | 75% | 0.78750% |
| Non Carpted with low Traffic | 50% | 0.5250% |
| Non Carpted with heavy Traffic | 25% | 0.26250% |
| No Proper Road/Connectivity | 0% | 0.000% |
| Total | ||
| 100% | ||
| Total |


Begin connecting your Neighbourhood
Through close knit cooperation
Trade Items with your community and avoid long and dangerous trips to town
Our trading system allows community keep track of their local inventory. Those in need can request items while those with large surplus can provide and help their community.
No more running out of toilet paper. Hism allows it's user to closely monitor supply and logistics of their near-by area. Every aspect of hism is opt-in and information is shared with your privacy in mind.
Are you looking for toilet paper but are severely lacking in eggs for your omelet? cant find any at the store? Dont worry, hism has you covered. simply select from the neighbourhood section and start managing you inventory today.


Preparation time
less than 30 mins
Cooking time
less than 10 mins
Serves
Serves 1
Jacket potatoes are a healthy and cheap meal and can be livened up with lots of different toppings. This recipe gives a choice of three toppings. Cooking them in the microwave speeds up the process considerably, but loses the crunchy jacket. By following the method below, the skin is kept dry which improves the texture when cooked.
Wash the potato and prick with a sharp knife several times on all sides.
Dry the potato well with kitchen paper and place on a microwave-safe plate.
Place in the microwave and cook on full power for four minutes.
Remove the plate using oven gloves and turn the potato over. Dry the potato and the plate and put back into the microwave.
Heat on full power for a further four minutes.
Remove the plate and leave the potato to stand for a minute, as it will continue to cook. Check that the potato is soft by pushing a sharp knife into the centre. Return to the microwave for another 30 seconds if it is still hard in any part.
For the leek, apple, cheese and bacon filling, wash and slice the leek. Place in a small bowl and grind over some black pepper, if using. Cover the bowl with cling film, leaving a small area open, and microwave on full power for two minutes. Grate the cheese, chop the bacon and grate the apple into the leeks.
Cut the potato in half, scoop out the fluffy middle and add to the cheese and vegetables. Mix well and spoon back into the ‘jackets’. Put the filled ‘jackets’ on a microwave-safe plate and heat for one minute, or until the cheese has melted.
For the tuna and sweetcorn, open the cans of tuna and sweetcorn and drain, then tip into the bowl with the mayonnaise and mix with black pepper, if using.
Split the jacket potato in half, roughly mash the middle with a fork, and spoon over the topping.
For the salmon and peas, put the peas into a mixing bowl and pour over boiling water from the kettle. Leave for five minutes, then drain and return the peas to the bowl.
Open the can and drain the salmon, then add to the peas in the mixing bowl.
Measure in the salad cream and mix well.
Split the jacket potato in half, roughly mash the middle with a fork, and spoon over the topping.
For the mushroom and tomato filling, wipe the mushrooms clean with a piece of damp kitchen paper. Slice them and place into a microwave-safe bowl and grind over some black pepper, if using. Microwave on full power for one minute, stir, and then heat for a further minute.
Allow to cool, then mix in the other ingredients.
Split the jacket potato in half, roughly mash the middle with a fork, and spoon over the topping.


Results
2
2
240
2
1
Steak House Restaurant
63 Birch Street
$2500
Apartment
Menu from: $6.50
Blue Chilli
1882 Trainer Avenue
$120
Restaurant
Saguaro Tavern
1882 Trainer Avenue
Restaurant


Note: browsers are likely to block the login popups. Please enable popups from this domain to prevent the browser from blocking them.


You can reach this dialog via the menu entry Analysis \ Symmetric Encryption (classic) \ Ciphertext-Only \ ADFGVX.
This dialog window supports you in analysing ADFGVX
encrypted messages.
The theoretical basis to analyze the ADFGVX cipher can be found here.
Just like the dialog ADFGVX Cipher: Key
Input, this dialog is divided into two sections, in which the two
stages of ADFGVX can be analyzed. However, the analysis of ADFGVX must be
carried out in reverse order: At first, the transposition (encryption step 2)
is analyzed, the second phase consists of analysing the substitution
(encryption step 1) and possibly you may discover that the transposition
password is not correct.
Step 2: Finding the Transposition Password
The dropdown fields for the Password length control the lower and upper
boundaries of the brute-force search for the transposition password. A large
search area will lead to a long wait while the computer works its way to the
upper boundary (as a reminder: a maximum password length of 6 characters
results in 1! + 2! + 3! + 4! + 5! + 6! = 873 possible combinations). As a rule
of thumb, passwords with a length up to 11 characters (43,954,713 possible
solutions) will be found in an acceptable time.
The edit field Current password shows the current transposition password.
Passwords found by the automatic analysis always consist of the first n letters
of the alphabet, n being the password length. Thus, the passwords
"MATRIX" and "CAEDBF" are equivalent. If the field is empty when beginning the
analysis, the search will cover the whole range defined by the minimal and
maximal password length fields. If a password is entered, the search will begin
with the given password and stop at the upper boundary. For example, with the
given password "CAEBDF" and an upper boundary of seven characters, the search
will terminate with the combination "GFEDCBA".
Entries made in this field will deny changes in the password length fields that
stand in contrast to the current password. For example, while the maximal
password length can be greater than the current length, it cannot be smaller.
To begin a new search within other boundaries, the current password must be
erased or changed.
Below the password text field, the current sequence for the column
transposition is displayed.
The button Apply bypasses the analysis of the transposition password.
This is especially useful with short messages, since in this case the bigram
analysis is unlikely to deliver a meaningful result. The entered password can
be used to transpose the message without being tested first. The bigram
analysis is carried out anyway, but not in order to assess the password. The
entries made into the substitution matrix can be faulty, they represent the
best, but not necessarily a good result of the analysis.
As long as no password is given in Current password, the button is
deactivated.
By clicking the button Analyze, the brute-force search for the
transposition key is started, beginning at the lower boundary or the current
password and stopping when it finds a possible password or reaching the upper
boundary.
For determining a possible solution, the current implementation searches for the
ADFGVX bigram with the highest relative frequency, matching it to the equivalent
character from the reference text selected in CrypTool text options.
In spite of this very crude criterion, there is almost
no occurrance of false alarms (disregarding the cases of pair wise
column shifts).
Step 1: Finding the Substitution Key
If a possible solution is found, the search stops and the substitution matrix is
filled, using a histogram generated from the reference text selected in the text options dialog
The Current solution of the analysis is displayed at the bottom of the
dialog, small letters indicate the parts that are already resubstituted,
capital letters are ADFGVX bigrams. The first bigram letter marks the row, the
second marks the column of the plaintext letter in the substitution matrix.
The user now has to try to detect whole words in the text and assign
the missing plaintext letters to the ADFGVX bigrams.
The Substitution matrix can only contain the letters 'A' to 'Z' and the
figures '0' to '9'. On repeated entry of an existing character, a dialog box is
displayed, giving the user the possibility to erase the old entry or to undo
the change.
The button Clear matrix erases all entries of the substitution matrix.
The button Standard matrix fills the substitution matrix with all 36
allowed characters in order.
Since the field Current solution is not updated dynamically,
clicking the button Update current solution will do just this.
If, by looking at the text, one does not discover any meaningful words, the
transposition password may be incorrect. In this case the transposition
analysis must be resumed by clicking Analyze and the substitution
analysis must be restarted with the next possible transposition password.
This step can be repeated until the upper boundary of the password search is
reached.
Clicking on the insert key icon
inserts an ADFGVX key that was previously copied
to the internal key store (if the button is
inactive/gray, there is no ADFGVX key available).
By clicking the Output button the current solution is written to a
new text window and the analysis dialog is closed.
The checkbox Show opening dialog determines, whether the short
information about how to analyze an ADFGVX-message is displayed when opening
the dialog.


Partitioning SSTotal.
The variation in the response (SSTotal) can be partitioned as the sum of the variability of interest (SSModel) and the unexplained variation (SSError):
\begin{equation*}
SSTotal = SSModel + SSError
\end{equation*}
Moreover, the degrees of freedom are also partitioned:
\begin{equation*}
\text{df total} = \text{df model} + \text{df error}
\end{equation*}


--- layout: layout-container name: Accounts Payable Entity Reference title: Accounts Payable Entity Reference order: 10 published: true showInNav: true back_to_top: true showBreadcrumbs: true ---
Updated: August 3, 2016
This topic describes the entity and type representations for common items used by the Accounts Payable API.
For more information about working with the SKY API, see the Getting Started guide.
The vendor filters entity has the following properties:
| Property | Type | Description |
|---|---|---|
| offset | integer | The number of records to skip, for use with pagination. |
| limit | integer | The number of records to return. If not specified, the default is 100. The maximum allowed value is 1000. |
| vendor_name | string | The name of the vendor. |
| status | string | The status of the vendor. |
| ui_vendor_id | string | The UI defined ID for the vendor. |
The vendor summary entity has the following properties:
| Property | Type | Description |
|---|---|---|
| vendor_id | integer | Vendor identifier. |
| vendor_name | string | The name of the vendor. |
| balance_due | number | The balance due on this vendor. |
| ui_defined_id | string | The UI defined Id of this vendor. |
| customer_number | string | The customer number. |
| vendor_status | string | The status of the vendor. |
| issue_1099s | boolean | Whether to issue 1099s to this vendor. |
| primary_address | vendor address | The primary address of the vendor. |
| payment_method | string | The default payment of this vendor. |
The vendor address entity has the following properties:
| Property | Type | Description |
|---|---|---|
| address_id | integer | The address identifier. |
| description | string | The description for this address. |
| country | string | The country for the address. |
| city | string | The city for the address. |
| county | string | The county for the address. |
| state | string | The state or province (or suburb in NZ) for the address. |
| postal | string | Refers to the Postal Code or ZIP of the address. |
| address_line | string | The street for this address. |
| is_primary | boolean | If this address is the primary address. |
| is_invoices | boolean | If invoices are sent to this address. |
| is_pos | boolean | If POs are sent to this address. |
| is_1099 | boolean | If 1099s are sent to this address. |
| title | string | The title for the primary contact. |
| first_name | string | The first name of the primary contact. |
| middle_name | string | The middle initial or name of the primary contact. |
| last_name | string | The last name of the primary contact. |
| suffix | string | The suffix of the primary contact. |
| position | string | The position of the primary contact. |
| address_contact_methods | array of address contact methods | The list of contact methods for this address. |
The address contact method entity has the following properties:
| Property | Type | Description |
|---|---|---|
| contact_method_id | integer | The address contact method identifier. |
| contact_type | string | The type of contact (email, phone, etc). |
| contact_info | string | The contact information (email address, phone number, etc) for this method. |
The vendor payment default entity has the following properties:
| Property | Type | Description |
|---|---|---|
| has_credit_limit | boolean | Whether or not this vendor has as credit limit. |
| credit_limit | number | The credit limit, if any. |
| payment_terms | string | The terms of the payment (NET D). |
| account_name | string | The account from which to pay invoices. |
| payment_method | string | The payment method for this invoice. |
| payment_option | string | The payment option for this invoice. |
The vendor detail entity has the following properties:
| Property | Type | Description |
|---|---|---|
| vendor_id | integer | Vendor identifier. |
| vendor_name | string | The name of the vendor. |
| balance_due | number | The balance due on this vendor. |
| ui_defined_id | string | The UI defined ID for this vendor. |
| customer_number | string | The customer number. |
| vendor_status | string | The status of the vendor. |
| issue_1099s | boolean | Whether to issue 1099s to this vendor. |
| addresses | array of vendor addresses | The address(es) of the vendor. |
| vendor_payment_default | vendor payment default | The default payment of this vendor. |
The vendor note action entity has the following properties:
| Property | Type | Description |
|---|---|---|
| note_action_id | integer | The note/action identifier. |
| note_type | string | The type - note or action. |
| date | string | The date for this note/action. |
| content | string | The content of this note/action. |
| description | string | The description for this note/action. |
| type | string | The type of the note/action. |
| is_complete | boolean | Whether this note/action is complete. |
| assign_to | string | To whom this note/action is assigned. |
| completed_date | string | The date on which this note/action was completed. |
The invoice filters entity has the following properties:
| Property | Type | Description |
|---|---|---|
| offset | integer | The number of records to skip. |
| limit | integer | The number of records to return. If not specified, the default is 100. The maxiumum allowed value is 1000. |
| to_date | date-time | Filter for invoices before a certain date. |
| from_date | date-time | Filter for invoices after a certain date. |
| invoice_status | string | Filter by the status of the invoice. |
| vendor_name | string | Filter by vendor name. |
The invoice summary entity has the following properties:
| Property | Type | Description |
|---|---|---|
| invoice_id | integer | The invoice identifier. |
| invoice_number | string | The number for the invoice. |
| invoice_date | date-time | The date for this invoice. |
| vendor_id | integer | The vendor identifier associated with this invoice. |
| vendor_name | string | The name of the vendor associated with this invoice. |
| vendor_status | string | The status of the vendor. |
| amount | number | The amount for this invoice. |
| description | string | The description of this invoice. |
| status | string | The status of this invoice. |
| invoice_post_status | string | The post status of this invoice. |
| balance | number | The balance on this invoice. |
| is_past_due | boolean | Whether this invoice is past due. |
| amount_due | number | The amount due on this invoice. |
| remit_to | string | The account number to which to remit for this invoice. |
| payment_method | string | The method to which to pay this invoice. |
| create_separate_payment | boolean | Whether to create a separate payment for invoice. |
| age | string | The age of this invoice. |
The invoice detail entity has the following properties:
| Property | Type | Description |
|---|---|---|
| invoice_id | integer | The invoice identifier. |
| vendor_id | integer | The vendor identifier associated with this invoice. |
| vendor_name | string | The name of the vendor associated with this invoice. |
| invoice_number | string | The number for the invoice. |
| invoice_date | date-time | The date for this invoice. |
| due_date | date-time | The due date for this invoice. |
| amount | number | The amount for this invoice. |
| balance | number | The balance on this invoice. |
| total_paid | number | The total amount paid on this invoice. |
| description | string | The description of this invoice. |
| approval_status | string | The approval status of this invoice. |
| invoice_payment_details | invoice payment details | The payment details for this invoice. |
| post_status | string | The post status of this invoice. |
| post_date | date-time | The post date for this invoice. |
| distribute_discounts | boolean | Whether to distribute discounts on this invoice. |
| distributions | array of distributions | The distributions on this invoice. |
The invoice payment details entity has the following properties:
| Property | Type | Description |
|---|---|---|
| remit_to | remit to address | The address to which to remit for this invoice. |
| payment_method | string | The method with which the invoice will be paid. |
| paid_from | string | The bank from which payments are made. |
| hold_payment | boolean | Whether to hold payment on this invoice. |
| create_separate_payment | boolean | Whether to create a separate payment for this invoice. |
| payments | array of invoice payment summaries | The payments on this invoice. |
The remit to address entity has the following properties:
| Property | Type | Description |
|---|---|---|
| address_id | integer | The address identifier. |
| description | string | The description for this address. |
| country | string | The country for the address. |
| city | string | The city for the address. |
| county | string | The county for the address. |
| state | string | The state or province (or suburb in NZ) for the address. |
| postal | string | Refers to the Postal Code or ZIP of the address. |
| address_line | string | The street for this address. |
| contact_name | string | The full name of the contact for this address. |
The invoice payment summary entity has the following properties:
| Property | Type | Description |
|---|---|---|
| payment_date | date-time | The date of this payment. |
| transaction_number | string | The transaction number for this payment. |
| payment_status | string | The status for this payment. |
| amount | number | The amount of this payment. |
| br_transaction_id | integer | The bank register transaction identifier for this payment. |
| checks_7_id | integer | The Checks identifier for this payment (FE 7). |
The distribution entity has the following properties:
| Property | Type | Description |
|---|---|---|
| distribution_id | integer | The identifier for this distribution. |
| distribution_split | array of distribution splits | The splits on this distribution. |
| amount | number | The distribution amount. |
| description | string | The description for this distribution. |
| account_number | string | The account number for this distribution. |
| type_code | string | The journal entry transaction type (debit or credit). |
The distribution split entity has the following properties:
| Property | Type | Description |
|---|---|---|
| distribution_split_id | integer | The identifier for this distribution split. |
| ui_project_id | string | The project id for this split. |
| transaction_code_values | array of transaction code values | The transaction codes and values for this split. |
| amount | number | The amount for this distribution split. |
| percent | number | The amount percentage for this distribution split. |
The transaction code value entity has the following properties:
| Property | Type | Description |
|---|---|---|
| name | string | The name for this transaction code. |
| value | string | The value for this transaction code. |


earlyreg.Rd
earlyreg
is a function to calculate the slope and intercept of an
amplification curve data from a quantitative PCR experiment. The number
of cycles to be analyzed is defined by the user (default 6 cycles).
The output contains the Maximal Information Coefficient (MIC), which
can be interpreted as a correlation measure with a range of [0,1].
A value of 0 mean statistically independent data and 1 approaches
in "probability for noiseless functional relationships" (see
original study by Reshef, D. N. et al. Detecting novel associations in
large data sets. Science, 334, 1518-1524 (2011)).
earlyreg(x, y, range = 5, normalize = FALSE)
| x | is the cycle numbers (x-axis). |
|---|---|
| y | is the cycle dependent fluorescence amplitude (y-axis). |
| range | is the number of cycles to be used for the regression. |
| normalize | is a logical parameter which indicates if the amplification curve data should be normalized to the 99 percent percentile of the amplification curve. |
# Calculate slope and intercept on noise (negative) amplification curve data # for the cycles 2 to 7 for the C316.amp data set library(chipPCR) data(C316.amp) # Plot the data plot(C316.amp[, 2], y=C316.amp[, 3], xlab="Cycle", ylab="RFU", main="C316.amp data set", lty=1, type="l")res <- earlyreg(x=C316.amp[, 2], y=C316.amp[, 3], range=5) res#> intercept slope sigma #> 123.906508 -27.507859 4.414113


David Higgins is a Web developer and designer based in Ireland. Hobbyist hacker, programmer, and all round web geek. Involved in the frontend scene for over 10 years now. I love a good problem. Currently available for work.
| Position | Company | Hired |
|---|---|---|
| Web Developer | Investment Management Fund | 2012 |
| Web Developer | MaxCDN | 2012 |
| Web Developer | Junerodgers.ie | 2011 - present |
| Web Developer | PopartDublin.com | 2012 - present |
Social


Input()
is used to instantiate a Keras tensor.
tf.compat.v1.keras.Input
tf.compat.v1.keras.layers.Input
tf.compat.v2.keras.Input
tf.compat.v2.keras.layers.Input
tf.keras.layers.Input
tf.keras.Input( shape=None, batch_size=None, name=None, dtype=None, sparse=False, tensor=None, ragged=False, **kwargs )
A Keras tensor is a tensor object from the underlying backend (Theano or TensorFlow), which we augment with certain attributes that allow us to build a Keras model just by knowing the inputs and outputs of the model.
For instance, if a, b and c are Keras tensors,
it becomes possible to do:
model = Model(input=[a, b], output=c)
The added Keras attribute is:
_keras_history
: Last layer applied to the tensor.
the entire layer graph is retrievable from that layer,
recursively.
shape
: A shape tuple (integers), not including the batch size.
For instance, shape=(32,)
indicates that the expected input
will be batches of 32-dimensional vectors. Elements of this tuple
can be None; 'None' elements represent dimensions where the shape is
not known.batch_size
: optional static batch size (integer).name
: An optional name string for the layer.
Should be unique in a model (do not reuse the same name twice).
It will be autogenerated if it isn't provided.dtype
: The data type expected by the input, as a string
(float32
, float64
, int32
...)sparse
: A boolean specifying whether the placeholder to be created is
sparse. Only one of 'ragged' and 'sparse' can be True.tensor
: Optional existing tensor to wrap into the Input
layer.
If set, the layer will not create a placeholder tensor.ragged
: A boolean specifying whether the placeholder to be created is
ragged. Only one of 'ragged' and 'sparse' can be True. In this case,
values of 'None' in the 'shape' argument represent ragged dimensions.
For more information about RaggedTensors, see
https://www.tensorflow.org/guide/ragged_tensors.**kwargs
: deprecated arguments support.A tensor
.
# this is a logistic regression in Keras x = Input(shape=(32,)) y = Dense(16, activation='softmax')(x) model = Model(x, y)
Note that even if eager execution is enabled,
Input
produces a symbolic tensor (i.e. a placeholder).
This symbolic tensor can be used with other
TensorFlow ops, as such:
x = Input(shape=(32,)) y = tf.square(x)
ValueError
: in case of invalid arguments.


[1]
pretty simple phone touch scrolling dos n't suffice for ring-tones.
[2]
since the top of weeks with size limitations with using music files Idiots.


This example demonstrates vertical scrolling using mouseover links. Scroll speed is adjustable.
Mouse down on the arrows to see the speed double. Original speed resumes on mouseup.
The code supports the capability to hide or swap images when the end is reached. Further information is provided upon request to licensed users of the code.
Content repeated for your scrolling pleasure :)
This example demonstrates vertical scrolling using mouseover links. Scroll speed is adjustable.
Mouse down on the arrows to see the speed double. Original speed resumes on mouseup.
The code supports the capability to hide or swap images when the end is reached. Further information is provided upon request to licensed users of the code.
Back to index


Next: package-shadowing-symbols, Previous: package-name, Up: Packages Dictionary
package-nicknames
package ⇒ nicknames
package—a package designator.
nicknames—a list of strings.
Returns the list of nickname strings for package, not including the name of package.
(package-nicknames (make-package 'temporary :nicknames '("TEMP" "temp"))) ⇒ ("temp" "TEMP")
Should signal an error of type type-error if package is not a package designator.


LIVING OUT LOUD by DeWyNGaLe Rating: B+
http://members.aol.com/DeWyNGaLe
Living Out Loud is the tale of adults and what life is like for them in their middle age years. It portrays life realistically, not like some other films do. Judith Nelson, played by Holly Hunter, is the center of attention in this film. Judith is a woman who has been recently separated from her husband who was cheating on her while they were married. She now lives alone, and doesn't have a lot to do. She loves to watch her favorite singer, Liz Bailey, played by Queen Latifah perform. She also likes to meet people and talk to people. She likes to observe others. One night coming home, she meets a man who runs the elevator. His name is Pat, and he is played by the very talented actor Danny DeVito. They get to talking and Judith comes to find out that he recently lost his daughter. Out of sympathy, she invites him for coffee, and the two get to know each other. Throughout the film, the two become close friends. Judith also forms a friendship with Liz after one of her performances. The rest of the film just shows these three interesting people and what goes on in their day to day lives.
The relationship between Pat and Judith is so realistic and developed. Pat falls in love with Judith, but she does not have the same feelings for him. The two continue to get to know each other and end up being the closest of friends. Judith is glad she has another friend, but she still isn't happy with her life. She doesn't want her life to be wasted. She wants to live her life fully.  On the other hand, the divorced Pat feels completely differently.
Living Out Loud is one of the best comedies of the year. There isn't much to the cinematography or the sound to this one, but it is a very open, true to life comedy, which makes it all the funnier. Some of the funniest sequences in the movie are when Judith starts daydreaming about the way she pictures things, or the way she wants life to be. Sometimes these daydreams are not so funny though, but they are very sad and emotional. Judith is very open to life, and that's what makes her one of the best characters in a movie I have seen in awhile.
The best thing in Living Out Loud is the fact that the adults portrayed in the film are very real to life. They seem like middle-aged people are, rather than characters that seem like they are still very young. Danny DeVito in particular played his part very realistically. His character of Pat was a very likable one, and also one that you sympathized for very easily. Holly Hunter's character was also a great one that brought tons of laughs. She was a very interesting person, and that's what made the character all the more likable. Holly Hunter was wonderful as Judith. Judith was a character that had suffered many hardships in her life. All of the characters, including Queen Latifah's Liz, are extremely interesting people. There isn't much plot in Living Out Loud. It doesn't really seem like the film is a film at all, but more of a documentary on real life people. It seemed like I was watching these people secretly, without them knowing it.
The Bottom Line- A true to life, emotional film about people that almost seem real. Not actors.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Time Search by Example Test
Selected Vital Group:
Selected Vital Name:
Dynamic Time Warping Scan Results
(best matching segments listed first)


Service to be held in NC for former US Sen. Kay Hagan
by The Associated PressGREENSBORO, N.C. (AP) — Family and friends will gather to remember former U.S. Sen. Kay Hagan of North Carolina, who died of a rare virus at the age of 66.
The service for Hagan will be held at 2 p.m. Sunday at First Presbyterian Church in Greensboro, where she lived for decades. A Hagan family spokeswoman has said the church service will be open to the public and followed by a visitation with the family.
About three years ago, Hagan contracted a rare virus spread from ticks to humans, leading to brain inflammation that made it difficult for her to speak and walk. She died Monday.
The Democrat was elected to the U.S. Senate in 2008, after a 10-year state legislative career. Hagan served one term before losing to Republican Thom Tillis in 2014.
The Associated Press