Firebird 2.1 Release Notes

More documents

Recommendations

Info

General Notes • Dmitry has addressed a complaint about slowness in executing cross joins across three or more tables, particularly when one or more tables are empty. See the notes here and Tracker item CORE-2200. Patch Release 2.1.1 Firebird 2.1.1 is a patch release that corrects a number of bugs, regressions or shortcomings that were reported following the v.2.1 final release. Included are fixes for the problems that made the nBackup utility unserviceable in that release, some changes to improve the new database monitoring feature's handling of a heavily loaded system and other changes to address complaints of slowness in some DML operations. For details, refer to the latest version of the Bugfix document accompanying these notes. Important It was discovered that, until now, Firebird's security database had been created with Forced Writes OFF. Like any database with FW disabled, the security database is vulnerable to corruption in an environment where the power supply is not guaranteed to be stable. The v.2.1.1 sub-release and all future builds rectify this situation and create security2.fdb with FW ON. If you are importing an existing security database from any older release, it is recommended that you use the gfix utility to activate Forced Writes. Note, however, that setting Forced Writes ON in any database on a Firebird 1.5.x or lower version server on Linux will have no effect. FW does not work on Linux in these lower Firebird servers. About These Notes Editions of the v.2.1 release notes are merged with the notes developed over the course of developments and releases from V.2.0 to this v.2.1.x release. Note that the separate v.2.0.x documentation is not distributed with the v.2.1 binaries. The Installation, Migration/Compatibility and Bug Fixes sections have been removed from the release notes document and are now distributed in the $fbroot$/doc/ subdirectory as separate documents. Like the release notes, they cover both the v.2.0.x and v.2.1 release series. To help smoothe the transition from older versions, it will be essential to study both the release notes and the migration/installation guide thoroughly. We encourage you to take your time testing this release with your applications and stressing it with real-world data and loads. Some legacy queries might not work, or might not perform as they did previously, due to a number of logic corrections that have been implemented. Temporary workarounds for legacy applications in such situations are available in some cases. We prefer that you research such issues in the documentation before you consider posting support questions or bug reports about them. From the QA Team Although this is a designated stable release, intended for production environments, it does introduce much that is new. We encourage you to see what you can achieve with these new features and let us know about any deficiency, sooner rather than later. You are enthusiastically invited to post to the firebird-devel list good descriptions of any bugs or beasts you encounter, or post bug reports directly to our Issue Tracker. Regular sub-releases will follow, whose quality and timeliness depend heavily on the reports that come in “from the field”. 4
General Notes Bug Reporting • If you think you have discovered a new bug in this release, please make a point of reading the instructions for bug reporting in the article How to Report Bugs Effectively, at the Firebird Project website. • If you think a bug fix hasn't worked, or has caused a regression, please locate the original bug report in the Tracker, reopen it if necessary, and follow the instructions below. Follow these guidelines as you attempt to analyse your bug: 1. Write detailed bug reports, supplying the exact build number of your Firebird kit. Also provide details of the OS platform. Include reproducible test data in your report and post it to our Tracker. 2. You are warmly encouraged to make yourself known as a field-tester by subscribing to the field-testers' list and posting the best possible bug description you can. 3. If you want to start a discussion thread about a bug or an implementation, please do so by subscribing to the firebird-devel list. In that forum you might also see feedback about any tracker ticket you post regarding this release. Additional Documentation You will find README documents for many of the new v.2 and v.2.1 features in your installation kit, installed by default in the /doc/ sub-directory. An automated "Release Notes" page in the Tracker provides access to lists and links for all of the Tracker tickets associated with this version and its various builds. Use this link. For your convenience, the many bug-fixes and regressions fixed during the development of Firebird 2.0.x and 2.1 are listed in descending chronological order in the separate Bugfixes document. —Firebird 2 Project Team 5
Page 1 and 2: Firebird 2.1 Release Notes Helen Bo
Page 4 and 5: Table of Contents 1. General Notes
Page 6 and 7: Firebird 2.1 Release Notes REVOKE A
Page 8 and 9: Firebird 2.1 Release Notes Authenti
Page 10 and 11: List of Tables 16.1. Firebird Devel
Page 12 and 13: Additions in this Sub-release Gener
Page 16 and 17: Chapter 2 New in Firebird 2 New Fea
Page 18 and 19: Procedural SQL New in Firebird 2 Do
Page 20 and 21: Derived Tables A. Brinkman New in F
Page 22 and 23: New in Firebird 2 • background -
Page 24 and 25: New in Firebird 2 From Firebird 1.0
Page 26 and 27: Important New in Firebird 2 The com
Page 28 and 29: Changes to the Firebird API and ODS
Page 30 and 31: isc_info_tra_isolation Changes to t
Page 32 and 33: Changes to the Firebird API and ODS
Page 34 and 35: Chapter 4 Global Improvements in Fi
Page 36 and 37: Global Improvements in Firebird 2.1
Page 38 and 39: Note Global Improvements in Firebir
Page 40 and 41: 2. File fragmentation Global Improv
Page 42 and 43: Global Improvements in Firebird 2.1
Page 44 and 45: Chapter 5 Data Definition Language
Page 46 and 47: Utilities Support for Database Trig
Page 48 and 49: Use Column Aliases in CREATE VIEW F
Page 50 and 51: 2. Data Definition Language (DDL) A
Page 52 and 53: SEQUENCE INDEX ROLE CHARACTER SET C
Page 54 and 55: Data Definition Language (DDL) SQL>
Page 56 and 57: • UNION DISTINCT • Improved Typ
Page 58 and 59: Data Manipulation Language (DML) )
Page 60 and 61: Format Data Manipulation Language (
Page 62 and 63: 3. 4. RETURNING ID INTO :PK; DELETE
Page 64 and 65:
Example Data Manipulation Language
Page 66 and 67:
[RETURNING ] Data Manipulation Lang
Page 68 and 69:
Enhancements to Functions A. dos Sa
Page 70 and 71:
CAST(x as ) A. dos Santos Fernandes
Page 72 and 73:
Data Manipulation Language (DML) bu
Page 74 and 75:
Data Manipulation Language (DML) BE
Page 76 and 77:
ROLLBACK RETAIN Syntax D. Yemanov D
Page 78 and 79:
Data Manipulation Language (DML) ii
Page 80 and 81:
Database: proc.fdb SQL> create tabl
Page 82 and 83:
Data Manipulation Language (DML) CU
Page 84 and 85:
Data Manipulation Language (DML)
Page 86 and 87:
::= NATURAL Data Manipulation Lang
Page 88 and 89:
Example Data Manipulation Language
Page 90 and 91:
::= '(' ')' Conclusions Data Manip
Page 92 and 93:
Chapter 7 Procedural SQL (PSQL) A h
Page 94 and 95:
... END Procedural SQL (PSQL) Conte
Page 96 and 97:
Procedural SQL (PSQL) Arguments wit
Page 98 and 99:
LEAVE [] Procedural SQL (PSQL) wher
Page 100 and 101:
IF (NEW.ID = 3) THEN EXECUTE PROCED
Page 102 and 103:
Chapter 8 New Reserved Words and Ch
Page 104 and 105:
SQRT (v.2.1)
Page 106 and 107:
For All Databases Indexing & Optimi
Page 108 and 109:
Indexing & Optimizations Matching o
Page 110 and 111:
Indexing & Optimizations Selectivit
Page 112 and 113:
Well-formedness checks Internationa
Page 114 and 115:
collation ES_ES collation PT_BR col
Page 116 and 117:
intl_module fbintl collation NAME [
Page 118 and 119:
Format: DISABLE-EXPANSIONS={0 | 1}
Page 120 and 121:
Create the procedures in the databa
Page 122 and 123:
Administrative Features • Regular
Page 124 and 125:
Administrative Features MON$AUTO_UN
Page 126 and 127:
Administrative Features SELECT MON$
Page 128 and 129:
Administrative Features Any process
Page 130 and 131:
Chapter 12 Security In this chapter
Page 132 and 133:
Security • the lack of protection
Page 134 and 135:
Security Simply omitting the user a
Page 136 and 137:
Security The main reason to restric
Page 138 and 139:
Caution with LegacyHash Security As
Page 140 and 141:
Command-line Utilities the Services
Page 142 and 143:
Command-line Utilities Undocumented
Page 144 and 145:
NBackup The functional responsibili
Page 146 and 147:
Command-line Utilities is a separat
Page 148 and 149:
Command-line Utilities • Even if
Page 150 and 151:
Command-line Utilities Therefore, p
Page 152 and 153:
Command-line Utilities -t(erminator
Page 154 and 155:
Help on command line switches Featu
Page 156 and 157:
External Functions (UDFs) If you ar
Page 158 and 159:
Chapter 15 A. Peshkov New Configura
Page 160 and 161:
A. Peshkov Note New Configuration P
Page 162 and 163:
New Configuration Parameters and Ch
Page 164 and 165:
Firebird 2 Project Teams Developer
Page 166 and 167:
New Built-in Functions Function For
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Appendix B: International Character
Page 178 and 179:
International Character Sets UTF-7
Page 180 and 181:
International Character Sets ibm-86
Page 182 and 183:
International Character Sets ibm-11
Page 184 and 185:
); COMMIT; Security Database Upgrad
show all

Firebird 2.1 Release Notes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?