Movatterモバイル変換

64.1. BKI File Format
Prev	Up	Chapter 64. BKI Backend Interface	Home	Next

64.1. BKI File Format

This section describes how thePostgres Pro backend interprets BKI files. This description will be easier to understand if thepostgres.bki file is at hand as an example.

BKI input consists of a sequence of commands. Commands are made up of a number of tokens, depending on the syntax of the command. Tokens are usually separated by whitespace, but need not be if there is no ambiguity. There is no special command separator; the next token that syntactically cannot belong to the preceding command starts a new one. (Usually you would put a new command on a new line, for clarity.) Tokens can be certain key words, special characters (parentheses, commas, etc.), numbers, or double-quoted strings. Everything is case sensitive.

Lines starting with# are ignored.

Prev	Up	Next
Chapter 64. BKI Backend Interface	Home	64.2. BKI Commands

By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp