Объявление UDF

← →
Alex Romanskiy © (2005-06-21 23:54) [0]

Как при объявлении UDF задать путь dll таким образом, что бы InterBAse искал ее не в папке InterBase\Bin , а в той же папке, в которой находится файл БД?
Спасибо.

← →
Digitman © (2005-06-22 08:50) [1]

никак.

IB-совместимые серверы ищут UDF-библиотеки в путях по дифолту (отн-но RootDirectory) и в путях, заданных явно в конфигурационных файлах соотв.серверов

вот фрагмент текста "Руководства разработчика" для IB6 :

UDF library placement

The rules for placing UDF libraries have changed since InterBase version 5. In InterBase 6
and later, InterBase finds a UDF library only if one of the following conditions is met:

The library is in interbase_home/UDF

The library in a directory other than interbase_home/UDF and the complete pathname to the
directory, including a drive letter in the case of a Windows server, is listed in the InterBase
configuration file.
InterBase finds the functions once you have declared them with DECLARE EXTERNAL
FUNCTION. You do not need to specify a path in the declaration.
The InterBase configuration file is called ibconfig on Windows machines and isc_config on
UNIX machines.
To specify a location for UDF libraries in a configuration file, enter a line of the following
form for Windows platforms:
EXTERNAL_FUNCTION_DIRECTORY "D:\Mylibraries\InterBase"
For UNIX, the line does not include a drive letter:
EXTERNAL_FUNCTION_DIRECTORY "/usr/local/lib/Mylibraries/InterBase"
Note that it is no longer sufficient to include a complete path name for the module in the
DECLARE EXTERNAL FUNCTION statement. You must list the path in the InterBase
configuration file if it is other than interbase_home/UDF.
IMPORTANT For security reasons, InterBase strongly recommends that you place your compiled
libraries in directories that are dedicated to InterBase libraries. Placing InterBase
libraries in directories such as C:\winnt40\system32 or /usr/lib permits access to all libraries
in those directories and is a serious security hole.

а вот фрагмент текста конфиг.файла FireBird :

# ----------------------------
# External Function (UDF) Paths/Directories
#
# UdfAccess may be None, Full or Restrict. If you choose
# Restrict, provide ";"-separated trees list, where UDF libraries
# are stored. Relative paths are treated relative to RootDirectory entry
# (see above). Default value "Restrict UDF" provides the same restrictions
# as in FB 1.0. To specify access to specific trees, enum all required
# paths (for Win32 this may be something like "C:\ExternalFunctions",
# for unix - "/db/extern;/mnt/extern").
#
# NOTE: THE EXTERNAL FUNCTION ENGINE FEATURE COULD BE USED TO COMPROMISE
# THE SERVER/HOST AS WELL AS DATABASE SECURITY!!
#
# IT IS STRONGLY RECOMMENDED THAT THIS SETTING BE USED TO LIMIT
# EXTERNAL FUNCTION LOCATIONS! SPECIALLY AVOID HAVING
# COMMON SUBTREES IN UdfAccess & ExternalFileAccess !
#
# Type: string (special format)
#
#UdfAccess = Restrict UDF

делай выводы

Объявление UDF Найти похожие ветки