. . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 11.1.4. SQL Statements for User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 11 by developers to communicate, through their applications, with the Firebird relational database management system. It has a long history. 1.1. Subject Matter The subject matter of this volume is wholly Keywords The primary construct in SQL is the statement. A statement defines what the database management system should do with a particular data or metadata object. More complex statements contain simpler

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 7.7.2. Management Statements in PSQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 13.2. SQL Statements for User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615 14. Management Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

сейчас HY012 Invalid transaction operation code Неверный код транзакции операции HY013 Memory management error Ошибка управления памятью HY014 Limit on the number of handles exceeded Достигнут лимит -820 335544881 need_difference Difference file name should be set explicitly for database on raw device. Файл разницы должен быть явно задан для базы данных на «сыром устройстве». -823 335544473 invalid_bookmark Unknown switch "@1". Неизвестный параметр командной строки "@1". -901 336330758 gbak_unknown_device Device type @1 not known. Тип устройства @1 не известен. -901 335544327 bad_req_handle Invalid request

-820 335544881 need_difference Difference file name should be set explicitly for database on raw device -823 335544473 invalid_bookmark Invalid bookmark handle -824 335544474 bad_lock_level Invalid lock required -901 336986118 fbsvcmgr_switch_unknown Unknown switch "@1" -901 336330758 gbak_unknown_device Device type @1 not known -901 335544327 bad_req_handle Invalid request handle -901 335740935 gfix_val_req Subsystem name -901 336723983 gsec_cant_open_db Unable to open database -901 336330767 gbak_unk_device Device type not specified -901 336723984 gsec_switches_error Error in switch specifications -901 335740945

336330757 gbak_switches_conflict Conflicting switches for backup/restore -901 336330758 gbak_unknown_device Device type not known -901 336330759 gbak_no_protection Protection is not there yet -901 336330760 gbak_db_exists Database already exists. To replace it, use the-R switch -901 336330767 gbak_unk_device Device type not specified -901 336330772 gbak_blob_info_failed Gds_$blob_info failed -901 336330773 "" -901 336330936 gbak_block_fac_specified A blocking factor may not be used in conjunction with device CT -901 336330940 gbak_missing_username User name parameter missing -901 336330941 gbak_missing_password

-901 335544326 bad_dpb_form Unrecognized database parameter block -901 336330758 gbak_unknown_device Device type %s not known -901 335740934 gfix_pgbuf_req Number of page buffers for cache required -901 use the- REP switch -901 335740942 gfix_pass_req Password required -901 336330767 gbak_unk_device Device type not specified -901 336723983 gsec_cant_open_db Unable to open database -901 335740943 gfix_subs_name "%s" -901 336330936 gbak_block_fac_specified A blocking factor may not be used in conjunction with device CT -901 336330940 gbak_missing_username User name parameter missing -901 336068796 dyn_role_does_not_exist

"suppress" Used in conjunction with the -v[erify] switch to redirect status messages to a file or device, rather than the screen, or to suppress them altogether. If -y suppress is used, then no information prevents that compression from taking place. -FA[CTOR] If backing up to a physical tape device, this switch lets you specify the tape’s blocking factor. -G[ARBAGE_COLLECT] The use of this switch

Firebird-Datenbanken müssen keine Dateien sein. Sie können auch auf einem sogenannten Rohgerät (engl. raw device) platziert werden, beispielsweise einer Festplattenpartition ohne Dateisystem. Die Frage, wo in

die von Entwicklern für die Kommunikation ihrer Anwendungen mit dem Firebird Relation Database Management System benötigt werden. 1.1. Thema Das Kernthema dieses Dokuments ist die vollständige Implementierung Möglichkeiten zum Erstellen von Datenbanken. Jaybird stellt zum Beispiel die Klasse org.firebirdsql.management.FBManager bereit, um programmgesteuert eine Datenbank zu erstellen. Bei Bedarf können Sie jederzeit error HY011 Attribute cannot be set now HY012 Invalid transaction operation code HY013 Memory management error HY014 Limit on the number of handles exceeded HY015 No cursor name available HY016 Cannot

supply a value. This command causes all the SQL commands being executed to be displayed on the output device prior to their execution. You may wish to turn echo off as part of a script file although the isql