mirror of
https://github.com/FirebirdSQL/firebird.git
synced 2025-01-22 16:43:03 +01:00
Builds/docs changes for ODS14
This commit is contained in:
parent
c91d779ff8
commit
5bdaa0aea6
@ -43,7 +43,7 @@ $ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName shell "rm -rf $AndroidDir
|
||||
$ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName shell "mkdir $AndroidDir"
|
||||
$ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName push gen/$InitialDebugTar $AndroidDir/
|
||||
$ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName shell "(cd $AndroidDir && tar xvf $InitialDebugTar)"
|
||||
$ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName shell "(cd $AndroidDir/firebird && ./common_test --log_level=all && ./libEngine13_test --log_level=all)"
|
||||
$ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName shell "(cd $AndroidDir/firebird && ./common_test --log_level=all && ./libEngine14_test --log_level=all)"
|
||||
$ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName shell "(cd $AndroidDir/firebird && ./AfterUntar.sh)"
|
||||
$ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName pull $AndroidDir/firebird/firebird.msg gen/Release/firebird/
|
||||
$ANDROID_HOME/platform-tools/adb -s $AndroidDeviceName pull $AndroidDir/firebird/security6.fdb gen/Release/firebird/
|
||||
|
@ -530,7 +530,7 @@
|
||||
#
|
||||
# Per-database & per-connection configurable.
|
||||
#
|
||||
#Providers = Remote,Engine13,Loopback
|
||||
#Providers = Remote,Engine14,Loopback
|
||||
|
||||
|
||||
# ----------------------------
|
||||
|
@ -151,10 +151,10 @@
|
||||
<CodeAnalysisRuleSet Condition="'$(Configuration)|$(Platform)'=='Release|x64'">AllRules.ruleset</CodeAnalysisRuleSet>
|
||||
<CodeAnalysisRules Condition="'$(Configuration)|$(Platform)'=='Release|x64'" />
|
||||
<CodeAnalysisRuleAssemblies Condition="'$(Configuration)|$(Platform)'=='Release|x64'" />
|
||||
<TargetName Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">engine13</TargetName>
|
||||
<TargetName Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">engine13</TargetName>
|
||||
<TargetName Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">engine13</TargetName>
|
||||
<TargetName Condition="'$(Configuration)|$(Platform)'=='Release|x64'">engine13</TargetName>
|
||||
<TargetName Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">engine14</TargetName>
|
||||
<TargetName Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">engine14</TargetName>
|
||||
<TargetName Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">engine14</TargetName>
|
||||
<TargetName Condition="'$(Configuration)|$(Platform)'=='Release|x64'">engine14</TargetName>
|
||||
<OutDir Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">..\..\..\temp\$(PlatformName)\$(Configuration)\firebird\plugins\</OutDir>
|
||||
<OutDir Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">..\..\..\temp\$(PlatformName)\$(Configuration)\firebird\plugins\</OutDir>
|
||||
<OutDir Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">..\..\..\temp\$(PlatformName)\$(Configuration)\firebird\plugins\</OutDir>
|
||||
|
@ -127,7 +127,7 @@ or TCP localhost loopback.
|
||||
|
||||
On the server side, default provider configuration is:
|
||||
|
||||
Providers = Remote, Engine13, Loopback
|
||||
Providers = Remote, Engine14, Loopback
|
||||
|
||||
It means that if the remote provider fails to match the connection string (because of missing
|
||||
protocol / host parts), then the embedded engine handles the hostless connection. If you need
|
||||
|
@ -135,7 +135,7 @@ Win_Sspi, Legacy_Auth</I></FONT></P>
|
||||
<P STYLE="margin-bottom: 0in"><FONT SIZE=4><I>UserManager = Srp</I></FONT></P>
|
||||
<P STYLE="margin-bottom: 0in"><FONT SIZE=4><I>TracePlugin = fbtrace</I></FONT></P>
|
||||
<P STYLE="margin-bottom: 0in"><FONT SIZE=4><I>Providers =
|
||||
Remote,Engine13,Loopback</I></FONT></P>
|
||||
Remote,Engine14,Loopback</I></FONT></P>
|
||||
<P STYLE="margin-bottom: 0in"><FONT SIZE=4><I>WireCryptPlugin = Arc4</I></FONT></P>
|
||||
<P STYLE="margin-bottom: 0in"><FONT SIZE=4>This provides normal
|
||||
operation in server, client and embedded cases. If you want to add
|
||||
@ -158,10 +158,10 @@ default equals to plugin implementation's name (and it's factory name
|
||||
which is actually used in firebird.conf). Certainly in typical case,
|
||||
module contains one plugin, and that plugin works with only one
|
||||
configuration, and all 3 names are equal, and no more configuration
|
||||
is needed – for example libEngine13.so or Engine13.dll contains
|
||||
implementation of provider Engine13, and nothing else except record </FONT>
|
||||
is needed – for example libEngine14.so or Engine14.dll contains
|
||||
implementation of provider Engine14, and nothing else except record </FONT>
|
||||
</P>
|
||||
<P STYLE="margin-bottom: 0in"><FONT SIZE=4>Providers = Engine13</FONT></P>
|
||||
<P STYLE="margin-bottom: 0in"><FONT SIZE=4>Providers = Engine14</FONT></P>
|
||||
<P STYLE="margin-bottom: 0in"><FONT SIZE=4>in firebird.conf is needed
|
||||
to load it. But if you have something complex – configuration file
|
||||
plugins.conf will help you to have such plugin factories which you
|
||||
|
@ -47,7 +47,7 @@ attach stage.</FONT></P>
|
||||
</P>
|
||||
<P STYLE="text-indent: 0.39in; margin-bottom: 0in"><FONT SIZE=4>Next
|
||||
samples are with default configuration, which contains 3 providers:
|
||||
<B>Remote</B> (establish network connection), <B>Engine13</B> (main
|
||||
<B>Remote</B> (establish network connection), <B>Engine14</B> (main
|
||||
database engine) and <B>Loopback</B> (force network connection to
|
||||
local server for database name without explicitly given network
|
||||
protocol).</FONT></P>
|
||||
@ -59,7 +59,7 @@ provider in the list) at once redirects such call to <I>RemoteHost</I>.
|
||||
That's how typical client configuration works.</FONT></P>
|
||||
<P STYLE="text-indent: 0.39in; margin-bottom: 0in"><FONT SIZE=4>When
|
||||
database name does not contain network protocol (just <I>dbname</I>)
|
||||
<B>Remote</B> provider rejects it and <B>Engine13</B> provider comes
|
||||
<B>Remote</B> provider rejects it and <B>Engine14</B> provider comes
|
||||
to stage. It tries to open <I>dbname</I> – and in case of
|
||||
success we get embedded connection to the database. Pay attention –
|
||||
we do not need special embedded library to have embedded connection,
|
||||
@ -74,7 +74,7 @@ to open database file. This is normal case if database was not
|
||||
created by that user in embedded mode or if he was not explicitly
|
||||
given OS rights for embedded access to databases on given box.
|
||||
Moreover, setting access rights in such a manner is a requirement for
|
||||
correct superserver operation. So after failure of <B>Engine13</B> to
|
||||
correct superserver operation. So after failure of <B>Engine14</B> to
|
||||
access database <B>Loopback</B> provider is attempted for an attach.
|
||||
It does not differ much from <B>Remote</B>, but tries to access
|
||||
database <I>dbname</I> on a server running on local host. On windows
|
||||
|
@ -2121,7 +2121,7 @@ codes:</font></p>
|
||||
<p style="margin-bottom: 0cm"><font size="4" style="font-size: 14pt">DIR_GUARD
|
||||
– where guardian lock is stored (fb_guard)</font></p>
|
||||
<p style="margin-bottom: 0cm"><font size="4" style="font-size: 14pt">DIR_PLUGINS
|
||||
– plugins directory ([lib]Engine13.{dll|so})</font></p>
|
||||
– plugins directory ([lib]Engine14.{dll|so})</font></p>
|
||||
<p style="margin-bottom: 0cm"><br/>
|
||||
|
||||
</p>
|
||||
|
Loading…
Reference in New Issue
Block a user