|
47 | 47 | </P> |
48 | 48 | <P STYLE="text-indent: 0.39in; margin-bottom: 0in"><FONT SIZE=4>Next |
49 | 49 | samples are with default configuration, which contains 3 providers: |
50 | | -<B>Remote</B> (establish network connection), <B>Engine13</B> (main |
| 50 | +<B>Remote</B> (establish network connection), <B>Engine14</B> (main |
51 | 51 | database engine) and <B>Loopback</B> (force network connection to |
52 | 52 | local server for database name without explicitly given network |
53 | 53 | protocol).</FONT></P> |
|
59 | 59 | That's how typical client configuration works.</FONT></P> |
60 | 60 | <P STYLE="text-indent: 0.39in; margin-bottom: 0in"><FONT SIZE=4>When |
61 | 61 | database name does not contain network protocol (just <I>dbname</I>) |
62 | | -<B>Remote</B> provider rejects it and <B>Engine13</B> provider comes |
| 62 | +<B>Remote</B> provider rejects it and <B>Engine14</B> provider comes |
63 | 63 | to stage. It tries to open <I>dbname</I> – and in case of |
64 | 64 | success we get embedded connection to the database. Pay attention – |
65 | 65 | we do not need special embedded library to have embedded connection, |
|
74 | 74 | created by that user in embedded mode or if he was not explicitly |
75 | 75 | given OS rights for embedded access to databases on given box. |
76 | 76 | Moreover, setting access rights in such a manner is a requirement for |
77 | | -correct superserver operation. So after failure of <B>Engine13</B> to |
| 77 | +correct superserver operation. So after failure of <B>Engine14</B> to |
78 | 78 | access database <B>Loopback</B> provider is attempted for an attach. |
79 | 79 | It does not differ much from <B>Remote</B>, but tries to access |
80 | 80 | database <I>dbname</I> on a server running on local host. On windows |
|
0 commit comments