firebird gbak. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.4. Splitting The Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . be "suppress_output" rather than "suppress". This is an error in the documentation as the source code for gbak shows that the switch must be "suppress". The log file must not exist. If it does, the the current version of gbak, and after displaying a couple of error messages, exits with an error code of 1 as shown above by the echo command. This method does not attempt to backup any databases and0 码力 | 34 页 | 191.73 KB | 1 年前3
firebird gsplitFirebird Backup File Splitting Filter Norman Dunbar Version 1.2, 19 June 2020 Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Splitting Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . discuss the following: • Command line options for gsplit. • Gsplit options and their parameters. • Splitting backups using gsplit. • Joining backup chunks using gsplit. From Interbase 6.0, gsplit is no0 码力 | 10 页 | 103.73 KB | 1 年前3
firebird wire protocolthe Firebird wire protocol. Most of the information was obtained by studying the Firebird source code and implementing the wire protocol in the Firebird .NET provider and Jaybird (Firebird JDBC driver) content depend on the operation that initiated the response. 2.1. Generic response Int32 Operation code If operation equals op_response: Int32 Object handle Int64 Object ID Buffer Data (meaning depends Operation code If operation equals op_sql_response: Int32 Message count Buffer Response data (meaning depends on the operation). 2.3. Fetch response Chapter 2. Responses 4 Int32 Operation code If0 码力 | 40 页 | 213.15 KB | 1 年前3
firebird 40 language reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 7.7. Writing the Body Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . procedural SQL (PSQL) — for stored procedures, stored functions, triggers, and dynamically-executable code blocks. These are the areas addressed in this volume. This document does not cover configuration statements and PSQL modules. A comment can be any text specified by the code writer, usually used to document how particular parts of the code work. The parser ignores the text of comments. Firebird supports0 码力 | 778 页 | 3.43 MB | 1 年前3
Firebird 2.5 Language Reference. . . . . . . . . . . . . . . . . . . . . . . . 269 Table of Contents 6 7.6. Writing the Body Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . procedural language — procedural SQL (PSQL) — for stored procedures, triggers and dynamically-executable code blocks. These are the areas addressed in this volume. 1.2. Authorship The material for assembling conglomerate was warmly welcomed. However, it came without rights to existing documentation. Once the code base had been forked by its owners for private, commercial development, it became clear that the0 码力 | 521 页 | 2.30 MB | 1 年前3
firebird 30 sprachreferenzProzedursprache — procedural SQL (PSQL) — für gespeicherte Prozeduren, Trigger und dynamisch ausführbare Code Blöcke. Dies sind die Themen, die in diesem Dokument behandelt werden. 1.2. Urheberschaft Für die SQL-Anweisungen und PSQL-Modulen vorhanden sein. Ein Kommentar kann ein beliebiger Text sein, der vom Code-Autor angegeben wird und normalerweise verwendet wird, um zu dokumentieren, wie bestimmte Teile des angibt. Normalerweise ist dies nichts anderes als eine Sortierung basierend auf dem numerischen Code der Zeichen und eine grundlegende Zuordnung von Groß- und Kleinbuchstaben. Wenn für Strings ein Verhalten0 码力 | 701 页 | 3.12 MB | 1 年前3
firebird language reference 30 rusвозможности работы с массивами. Ниже приведён её текст: CREATE OR ALTER PROCEDURE SHOW_LANGS ( CODE VARCHAR(5), GRADE SMALLINT, CTY VARCHAR(15)) RETURNS ( LANGUAGES VARCHAR(15)) AS DECLARE VARIABLE BEGIN I = 1; WHILE (I <= 5) DO BEGIN SELECT LANGUAGE_REQ[:I] FROM JOB WHERE (JOB_CODE = :CODE) AND (JOB_GRADE = :GRADE) AND (JOB_COUNTRY = :CTY) AND (LANGUAGE_REQ IS NOT Пример 4.35. Таблица с полем массивом CREATE TABLE JOB ( JOB_CODE JOBCODE NOT NULL, JOB_GRADE JOBGRADE NOT NULL, JOB_COUNTRY COUNTRYNAME0 码力 | 719 页 | 3.98 MB | 1 年前3
firebird isqlutility to bail on error, but only when used in a non-interactive mode. The switch returns an error code to the Operating System. This switch was added to prevent isql from executing scripts after an error error has been detected. No further statements will be executed and isql will return an error code to the OS. Users still need to use the -e(cho) switch to echo commands to an output file, to isolate other than a semicolon. To change the terminator character to a tilde (‘~’) enter the following code: SQL> SET TERM ~ ; You must terminate this command with the current terminator of course! Changing0 码力 | 76 页 | 369.92 KB | 1 年前3
Firebird File and Metadata Security. . . . . . . . . . . . . . . . . . . . . 9 4.2.5. Deleting stored procedure and trigger source code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Embedded Firebird Server procedure and trigger source code When you write and define a stored procedure or trigger for a Firebird database, the server stores an almost complete copy of the procedure source code along with a “compiled” is executed by the server, the source code is not used. Some developers attempt to protect at least some of their database metadata by deleting the source code from the database before distributing0 码力 | 19 页 | 115.27 KB | 1 年前3
Firebird Internals: Inside a Firebird DatabaseMuch of the information in this manual has been extracted from the Firebird source code — mainly on the ODS related code and headers — and from some (partially out of date) documents on the Research part header. Various page types have an additional header that follows on from the standard one. The C code representation of the standard header is: struct pag { SCHAR pag_type; UCHAR pag_flags; and so on. If the database is multi-file, then each file will have a header page of its own. The C code representation of the database header page is: struct header_page { pag hdr_header; USHORT0 码力 | 63 页 | 261.00 KB | 1 年前3
共 29 条
- 1
- 2
- 3













