Firebird数据库开发详解：The_Firebird_Book精华指南

4星 · 超过85%的资源需积分: 10 133 浏览量更新于2024-08-02 2 收藏 13.58MB PDF 举报

"The Firebird Book: A Reference for Database Developers" 《Firebird开发书记：The Firebird Book》是一本专为数据库开发者编写的详尽参考指南，由Helen Borrie撰写，并由Henry Xu进行整理。这本书涵盖了Firebird数据库系统的安装、网络设置、配置以及基本操作等方面的知识，是Firebird开发者的宝贵资源。在安装部分（Chapter 1），书中详细介绍了Firebird的系统需求，如何获取安装包，包括针对Linux和Windows的不同安装步骤。对于新用户，书中有指导性的测试安装过程，以及如何设置嵌入式服务器和了解默认磁盘位置的信息。网络设置章节（Chapter 2）讨论了Firebird所需的网络协议，如命名管道、本地访问和跨平台混合环境下的连接。书中还阐述了如何为服务器指定网络地址，配置TCP/IP端口服务，并通过ping命令测试网络连接的可行性。配置Firebird章节（Chapter 3）中，读者将学习到数据库级别的配置，如环境变量的作用以及Firebird配置文件的使用。这部分内容对优化数据库性能和安全性至关重要。操作基础部分（Chapter 4）讲解了在Linux/UNIX和Windows平台上运行Firebird服务器的方法，数据库别名的创建，以及如何管理数据库。这部分内容旨在帮助开发者掌握日常的数据库运维技能。《Firebird开发书记：The Firebird Book》为开发者提供了从安装、配置到实际操作的全方位指南，是深入理解和有效利用Firebird数据库系统的重要参考资料。无论你是初学者还是经验丰富的开发者，都能从中受益，提升你的Firebird开发技能。欲了解更多详情，可以访问专业论坛http://www.firebird.net.cn或联系作者Henryxxf@163.com，或访问他的个人网站http://www.pplife.cn获取进一步的支持和交流。

Appendix VII: Firebird Limits enumerates the various physical limits applicable

to Firebird 1.0.x and 1.5 databases.

Appendix VIII: Character Sets and Collations is a full reference to the interna-

tional character sets and language-specific collation sequences distributed with

Firebird 1.5.

Appendix IX: System Tables and Views provides the data description specifica-

tions for the schema tables maintained by the Firebird server inside every data-

base. It includes source code listings for some useful views you can create to

interrogate the system tables.

Appendix X: Error Codes is a full, tabulated listing of the exception codes

(SQLCODE and GDSCODE) defined in Firebird 1.5, along with the associated

symbolic constants and the message texts in English.

Appendix XI: Reserved Words lists all of the SQL keywords that Firebird 1.0.x

and 1.5 treat as reserved words.

Appendix XII: Readings and Resources is a compilation of resources available

to Firebird users. It includes book and other documentary recommendations,

descriptions, and links to support forums.

The Glossary provides detailed descriptions of terminology and concepts you

are likely to encounter on your journey into Firebird. It was compiled from a sur-

vey of experienced and not-so-experienced Firebird community members who

were asked to provide a “wish list” for a glossary.

Firebird’s Origins

Developed as an ongoing open source project, Firebird is the first new-generation

descendant of Borland’s InterBase 6.0 Open Edition code, which was released for

open source development in July 2000 under the InterBase Public License (IPL).

The Firebird source code tree is maintained and developed on the international

open source code foundry, SourceForge.net (http://sourceforge.net), by a large

team of professional developers, comprising both volunteers and others in specialist

roles that are partly funded from community and commercial sources.

TIP The Firebird RDBMS products and several associated modules are dis-

tributed completely free of registration or deployment fees under a variety of

open source licenses. The Firebird project, its developers, and its software are

not associated with Borland Software Corporation in any way.

Introduction

xxv

2794fm.qxd 7/2/04 12:36 PM Page xxv

The Firebird Project

Development

The developers, designers, and testers who gave you Firebird and several of the drivers

are members of the Firebird open source project at SourceForge, an amazing virtual

community that is home to thousands of open source software teams. The Firebird

project’s address there is http://sourceforge.net/projects/firebird. At that site

are the CVS source code tree, the bug tracker, and a number of technical files that can

be downloaded for various purposes related to the development and testing of the

codebases.

The Firebird Project developers and testers use an e-mail list forum, firebird-

devel@lists.sourceforge.net, as their “virtual laboratory” for communicating with

one another about their work on enhancements, bug fixing, and producing new ver-

sions of Firebird.

Anyone who is interested in watching the progress and feedback on beta devel-

opment can join this forum.

Support for Application Developers and DBAs

Firebird has a powerful community of willing helpers, including a large body of active

developers with many years of experience developing with and deploying Firebird

and its InterBase ancestors. The esprit de corps among this large group is such that,

having acquired the skills and learned the “inside tricks” from the advice of others, its

members stay around the lists as mentors to new users. The mainstream free support

channel is the Firebird support forum.

More specialized groups within the project’s arena conduct specific forums—Java,

Delphi and C++Builder, tools, Visual Basic, .NET, PHP, and more. The groups run as

e-mail lists, and many are mirrored to a news server. The latest links to these forums

can always be found at the main community website, http://firebirdsql.org, and at

the affiliated IBPhoenix commercial site, http://www.ibphoenix.com.

The IBPhoenix site also hosts an enormous volume of searchable technical and

user documentation, links to third-party tools, and a running news board of events

happening throughout the Firebird community.

Refer to Appendix XII for a comprehensive compilation of support resources in

the community.

The FirebirdSQL Foundation

The FirebirdSQL Foundation (Inc.) is a non-profit foundation incorporated in New

South Wales, Australia, that raises funds around the world for grants to developers

working on general and special projects for extending, testing, and enhancing

Firebird. Funds come in through private and corporate sponsorships, donations, and

membership subscriptions. It provides a way for appreciative Firebird users to return

a contribution for the free use of software and community support. Look it up at

http://firebirdsql.org/ff/foundation.

Introduction

xxvi

2794fm.qxd 7/2/04 12:36 PM Page xxvi

Sparky

Sparky, a young, scarlet phoenix with a beaky grin, is

Firebird’s mascot. Sparky has been around the Firebird

project in various guises since the beginning, but he

emerged “in person” for the first time at the first inter-

national Firebird Conference in Fulda, Germany, in

May 2003.

Overview of Features

Firebird is a true client/server software, designed especially for use in local and

wide-area networks. Accordingly, its core consists of two main software programs:

the database server, which runs on a network host computer, and the client library,

through which users on remote workstations connect to and communicate with data-

bases managed by the server.

NOTE Administering and developing with a full-blooded SQL client/server

RDBMS may be new territory for you. It can present a steep learning curve if

this is your first venture into data management software that is purpose-built

for multiple concurrent writers. Part Two of this guide provides an introduction

to client/server concepts. If you find yourself getting lost in the following

descriptions, you might like to visit Part Two first to acquire some context.

Firebird Versions

Firebird version 1.0.x binaries were developed by correcting and enhancing the

modules, written in the C language, that the open source community inherited from

InterBase 6.0. For Firebird 1.5, the modules were completely rewritten in C++, with a

high degree of standardization across compilers.

The step from version 1 to version 1.5 is a major one “under the hood,” but the

application programming interface (API) is unchanged. Application software written

for version 1 requires little or no modification to work with version 1.5.

While it is recommended that you install and use the highest version available,

operating system incompatibilities—especially with respect to Linux—mean that the

highest 1.0.x version remains the only option for some sites. Many enhancements in

v.1.5 have been backported to v.1.0.x, with regular sub-releases.

Network Access

A Firebird server running on any platform accepts TCP/IP client attachments from

any client platform that can implement the Firebird API.

Clients cannot attach to a Firebird server through any medium of filesystem shar-

ing (NFS shares, Samba client connections, Windows shares or mapped drives, etc.).

Introduction

xxvii

2794fm.qxd 7/2/04 12:36 PM Page xxvii

A client must attach through an absolute physical path. However, from Firebird 1.5

onward, a database aliasing feature allows applications to “soft-connect” through

named aliases, whose absolute paths are configured specifically on each deployed

server.

A Firebird server running on a services-capable Windows host can accept attach-

ments from Windows clients through the Named Pipes network protocol.

Multi-generational Architecture

Firebird’s model for isolating and controlling the work of multiple users revolves

around an architecture that is able to store more than one version of a record in the

database concurrently. Multiple generations of a record can exist simultaneously—

hence the term “multi-generational.” Each user task holds its own contextual view

of database state (see the next section) and, when ready, writes its own versions of

records on the server’s disk. At that point, the new version (or a deletion) cannot be

accessed by other user tasks.

The most recently committed record version is the only one visible outside the

user task that successfully posted a new version, and it continues to be the version

seen by other tasks. Others will be aware that something has happened to the record

because they will be blocked from updating or deleting the same record until the new

version becomes “official” by being committed.

Because of its multi-generational architecture (known as MGA), Firebird has

no need for the two-phase locking used by other DBMSs to control multi-user

concurrency.

Transactions

All user tasks in Firebird are enclosed within transactions. A task begins with a START

TRANSACTION statement and ends when work posted by the user task is committed

or rolled back. A user task can make multiple requests for operations to be performed

within a single transaction, including operations in more than one database.

Work is saved to the database in two stages. In the first stage, changes are stored

to disk, without changing database state. In the second stage, changes are committed

or rolled back by the client process. In v.1.5 and higher, clients can “unpost” parts of

work by tagging stages in a process as savepoints and rolling back to a savepoint with-

out rolling back an entire transaction.

Firebird transactions are atomic, which means that all work posted in a transac-

tion will succeed or all will fail.

Every transaction is configurable, with three levels of isolation and a variety of

strategies for fine-tuning concurrency and read-write conditions.

Stored Procedures and Triggers

Firebird has a rich language of procedural extensions, PSQL, for writing stored proce-

dures and triggers. It is a structured language with support for FOR looping through

sets, conditional branching, exception handling, and event triggering. PSQL code is

compiled at creation and stored in binary form.

Introduction

xxviii

2794fm.qxd 7/2/04 12:36 PM Page xxviii

Trigger support is strong, with a Before and After phase for each DML event.

Multiple triggers may be stored for each phase/event and optionally numbered in an

execution sequence. Firebird 1.5 and higher support Before or After triggers that com-

prise behaviors for all three DML events, with conditional branching per event.

Referential Integrity

Firebird has full support for formal, SQL-standard referential integrity—sometimes

known as declarative referential integrity—including optional cascading updates and

deletes with a number of RI trigger action options.

Database Shadowing

Firebird servers can optionally maintain database shadows. A shadow is a real-time

copy of the database with some extra attributes that make it unavailable for reading

until it is made available by the server. Shadows can be “kicked in” if required, either

manually or automatically. The purpose of shadowing is to enable the database to

become available very quickly if a disk crash occurs.

Shadowing is not replication.

Security

Host Security

Firebird provides user access security to the server by means of user IDs and

encrypted passwords. Like any database server, it relies on adequate physical, net-

work access, and filesystem security being in place. Firebird can store encrypted data

but, except for password encryption, it provides no capability to encrypt data itself.

CAUTION While an embedded server application (see the “Embedded Server”

section) has its uses for single-user, stand-alone applications, it bypasses the

host's security gateway altogether. SQL privileges defined at database level still

apply, but an embedded application can get password-free access to any data-

base on the server. For the implications, refer to Chapter 34.

SQL Privileges

Although a user must be authorized to access a Firebird server, no user except the

SYSDBA and the database owner has automatic rights to anything within an individ-

ual database. Database-level security is supported on an “opt-in” basis, by means of

SQL privileges. Users must be granted privileges to any object explicitly.

Introduction

xxix

2794fm.qxd 7/2/04 12:36 PM Page xxix

剩余1081页未读，继续阅读

霁月当楼

粉丝: 9
资源: 35

Firebird数据库开发详解：The_Firebird_Book精华指南

Lazarus+ZeosDBO+FireBird开发指南：全面解析与实例

Lazarus+ZeosDBO+Firebird开发教程：版本规定与数据处理详解

Lazarus与Firebird智能开发：永磁同步电机控制技术结合ZeosDBO

FIREBIRD_connect.zip_Firebird_ODBC x64_firebird_firebird delphi

firebird language reference 30 rus_firebird_manual_language_Fire

The_Firebird_Book

node-firebird-libfbclient:Firebird SQL绑定

Test-Boolean-Firebird.zip_Will_boolean

firebird-documentation:火鸟文档

firebird-docker:火鸟Dockerfile

最新资源