isql utility that comes with Firebird and possibly some third-party editors — employ an internal convention that requires all statements to be terminated with a semi-colon. This creates a conflict with isql utility that comes with Firebird and possibly some third-party editors — employ an internal convention that requires all statements to be terminated with a semi-colon. This creates a conflict with could become invalid because the new description of the parameters is incompatible with the old calling format. For information on how to troubleshoot such a situation, see the article The RDB$VALID_BLR

isql utility that comes with Firebird and possibly some third-party editors — employ an internal convention that requires all statements to be terminated with a semi-colon. This creates a conflict with isql utility that comes with Firebird and possibly some third-party editors — employ an internal convention that requires all statements to be terminated with a semi-colon. This creates a conflict with values, so anything that changes them inside the procedure has no effect on the parameters in the calling program. Input parameters may have default values. Those that do have values specified for them

primary file and/ or secondary files are named using the ".gdb" extension that used to be the Borland convention for suffixing InterBase database file names. The issue is described in more detail in Other Win32

valid input like '' (an empty string). The main cause of this problem is that with “old style” UDF calling (inherited from InterBase), it is not possible to pass NULL as input to the function. When a UDF as old-style UDFs. 13.3. Improvements in Firebird 2 Firebird 2 comes with a somewhat improved calling mechanism for old-style UDFs. The engine will now pass NULL input as a null pointer to the function performs an undesired NULL <=> non-NULL conversion, you’ll have to anticipate it in your code before calling the UDF (see also Testing for NULL — if it matters, elsewhere in this guide). The declarations

not be running at all. In that case, go back to Testing your installation and fix the problem. Calling gsec on Linux On **nix systems, if you call gsec from its own directory, you should type ./gsec instead connection string to the client application (or, if you are a programmer, to the routines you are calling). A connection string uniquely identifies the location of the database on your computer, local network

ISC_PASSWORD. This version of the command will exit with a error code of zero.  This method of calling gbak will make a backup of the database. If your database is large, this can take some time to complete

connection string to the client application (or, if you are a programmer, to the routines you are calling). A connection string uniquely identifies the location of the database on your computer, local network

jedem Punkt des Codes zur endgültigen END-Anweisung springt, wodurch das Programm beendet wird. Calling EXIT in a function will result in the function returning NULL. EXIT-Beispiele Verwendung der EXIT-Anweisung CURRENT_USER || ' REFUSED.'); POST_EVENT 'CONNECTION ATTEMPT BY BLOCKED USER!'; END -- now calling an exception EXCEPTION EX_BADUSER; END END Siehe auch Transaktionssteuerung 7.7.21. POST_EVENT