unless you supply -⁠u[ser] and -⁠pa[ssword] on the command line. For example: linux> gfix -validate my_employee linux> Unable to perform operation. You must be either SYSDBA - or owner of the database reality, it is a single line. However, passing the username and password works: linux> gfix -validate my_employee -user sysdba -password masterkey You will notice, hopefully, that some commands do not give as follows: linux> isql my_employee; SQL> create shadow 1 manual '/home/norman/firebird/shadow/my_employee.shd1'; SQL> create shadow 2 manual '/home/norman/firebird/shadow/my_employee.shd2'; SQL> commit;

таблицу). CREATE TABLE my_table ( my_number integer not null primary key ) CREATE GENERATOR my_generator CREATE TRIGGER my_before_trigger FOR my_table BEFORE INSERT AS BEGIN IF (NEW.my_number IS NULL) NULL) THEN NEW.my_number = GEN_ID(my_generator, 1); END Переход с MS SQL на Firebird 10 CREATE PROCEDURE get_my_generator RETURNS (new_value INTEGER) AS BEGIN new_value = GEN_ID(my_generator, 1); MS-SQL */ CREATE PROCEDURE my_procedure AS DECLARE @my_variable int SET @my_variable = 5 /* Firebird */ CREATE PROCEDURE my_procedure AS DECLARE VARIABLE my_variable int; BEGIN my_variable = 5; END В обоих

c:\my_app\app.exe c:\my_app\gds32.dll c:\my_app\ib_util.dll c:\my_app\icudt30.dll c:\my_app\icuin30.dll c:\my_app\icuuc30.dll c:\my_app\firebird.conf c:\my_app\firebird.msg c:\my_app\intl\fbintl c:\my_app\intl\fbintl.dll c:\my_app\intl\fbintl.conf c:\my_app\udf\fbudf.dll Suppose you want to place the Firebird files (excluding the renamed fbembed.dll) in another directory. In that case, you need Firebird files. Example c:\my_app\app.exe c:\my_app\gds32.dll c:\my_app\ib_util.dll c:\my_app\icudt30.dll c:\my_app\icuin30.dll c:\my_app\icuuc30.dll c:\my_app\firebird.conf Installing

Example: $ isql Use CONNECT or CREATE DATABASE to specify a database SQL> CONNECT "C:\DATABASES\FIREBIRD\MY_EMPLOYEE.FDB" CON> user 'SYSDBA' password 'secret';  Here and elsewhere in this document, we use local database): SQL> CONNECT "C:\DATABASES\FIREBIRD\MY_EMPLOYEE.FDB" On Linux, a similar example would be: SQL> CONNECT "/databases/firebird/MY_EMPLOYEE.FDB" • If connecting remotely (using TCP/IP) connect to a database on a Windows server named cosmos: SQL> CONNECT 'cosmos:C:\DATABASES\FIREBIRD\MY_EMPLOYEE.FDB'  Firebird is slash agnostic and automatically converts either type of slash to suit

то он будет сохранён в базе данных как NULL. Пример: COMMENT ON DATABASE IS ' ('' Это тестовая my.fdb'') '; БД COMMENT ON TABLE METALS IS ' '; Справочник металлов COMMENT ON COLUMN METALS.ISALLOY случаев использования других наборов символов). 48 Руководство по языку SQL Пример: CREATE DATABASE "my.fdb" DEFAULT CHARACTER WIN1251 COLLATION WIN1251_UA Обратите внимание: Здесь используется ключевое команды ALTER DATABASE BEGIN BACKUP. Пример: ALTER DATABASE ADD DIFFERENCE FILE '/usr/opt/firebird/db/my.delta' Примечания: • Этот оператор в действительности не добавляет файла. Он просто переопределяет

This leads to the common questions on the Firebird lists along the lines of: “I want to…” “…protect my database design (table structures, stored procedures, triggers etc.) from all users of the database source code is also used by various utilities, such as my own DBak application — an alternative backup program to “gbak”. I have not bothered to write my own BLR decoder at this stage, so DBak relies on the their compiled binaries? Chapter 6. Other Forms of Obscurity 11 Chapter 7. Acceptable Low Security My comments so far have been directed at the idea of strong security and I guess the concept of security

shown in the following example which connects my Windows XP client version of gsec to my Linux server named ganymede and allows me to manage the users on my Linux server. C:\>gsec -database ganymede:/ Chapter 7. Gsec caveats The following is a brief list of gotchas and funnies that I have detected in my own use of gsec. Some of these are mentioned above, others may not be. By collecting them all here

and supply these to the external tool. To make this simpler for script writers, my own installation uses a standard in my aliases.conf file as follows: • The database alias must start in column one. the Firebird utilities either. • Databases are all single file databases. The last rule applies to my installation only and means that the following simple backup script will work. If multiple file databases Chapter 7. Gbak Caveats The following is a brief list of gotchas and funnies that I have detected in my own use of gbak. Some of these are mentioned above, others may not be. By collecting them all here

RDB$DATABASE Вызов внутри PSQL кода, второй необязательный параметр не указан: MY_VAR = ADD_INT(A); Пример 4.91. Создание детерминистической хранимой функции Пример 4.144. Добавление комментария для текущей базы данных. COMMENT ON DATABASE IS 'Это тестовая (''my.fdb'') БД'; Пример 4.145. Добавление комментария для таблицы. COMMENT ON процедурой: SELECT * FROM MY_TAB JOIN MY_PROC(MY_TAB.F) ON 1 = 1 Запрос же написанный следующим образом вызовет ошибку SELECT * FROM MY_PROC(MY_TAB.F) JOIN MY_TAB ON 1 = 1

using COMMENT ON 1. Adding a comment for the current database COMMENT ON DATABASE IS 'It is a test (''my.fdb'') database'; 2. Adding a comment for the METALS table COMMENT ON TABLE METALS IS 'Metal directory'; other streams: SELECT * FROM MY_TAB JOIN MY_PROC(MY_TAB.F) ON 1 = 1; Here, the procedure will be executed before a single record has been retrieved from the table, MY_TAB. The isc_no_cur_rec error error The solution is to use syntax that specifies the join order explicitly: SELECT * FROM MY_TAB LEFT JOIN MY_PROC(MY_TAB.F) ON 1 = 1; This forces the table to be read before the procedure and everything