mirror of
https://github.com/FirebirdSQL/firebird.git
synced 2025-01-22 18:43:02 +01:00
Updated docs.
This commit is contained in:
parent
e6448ad971
commit
c7374d3a99
@ -73,6 +73,7 @@ Usage
|
||||
[ -a[uto]* | -d[emand] ]
|
||||
[ -g[uardian] ]
|
||||
[ -l[ogin] username [password] ]
|
||||
[ -i[nteractive] ]
|
||||
|
||||
sta[rt] [ -b[oostpriority] ]
|
||||
sto[p]
|
||||
@ -181,30 +182,4 @@ user defined on a domain or locally on another server. In the above examples,
|
||||
SERVER\user
|
||||
With no prefix, the user is implicitly a local user on the current machine.
|
||||
|
||||
|
||||
Instsvc and the "local" client/server protocol
|
||||
==============================================
|
||||
|
||||
When Firebird is configured to run under a specific user--which is
|
||||
recommended for servers on wide networks--the "local" protocol is
|
||||
unavailable.
|
||||
|
||||
NOTE Regular user login is not compatible with the local access
|
||||
protocol. Local protocol needs the server and the client to
|
||||
interact by way of an emulated network layer using Windows messages.
|
||||
A service running under a specific user account runs in its own,
|
||||
isolated, virtual desktop environment and those messages cannot be
|
||||
delivered. It is necessary for local clients to connect using TCP/IP
|
||||
local loopback protocol (localhost server).
|
||||
|
||||
This is not a bug but, rather, implements a function of Windows
|
||||
NT/2K/XP design that has some shortcomings. In future releases,
|
||||
local protocol will be re-implemented, using proper inter-process
|
||||
communication mechanisms.
|
||||
|
||||
When Firebird is configured without a specific user (i.e. LocalSystem
|
||||
user in SERVICE_INTERACTIVE_PROCESS mode, "Allow service to interact
|
||||
with Desktop"), both TCP/IP local loopback and "local" protocols are
|
||||
available.
|
||||
|
||||
/* ends */
|
||||
|
28
doc/sql.extensions/README.current_time
Normal file
28
doc/sql.extensions/README.current_time
Normal file
@ -0,0 +1,28 @@
|
||||
----------------------------------
|
||||
CURRENT_TIME and CURRENT_TIMESTAMP
|
||||
----------------------------------
|
||||
|
||||
Function:
|
||||
Returns current server system time or date+time values.
|
||||
|
||||
Syntax rules:
|
||||
CURRENT_TIME [(<seconds precision>)]
|
||||
CURRENT_TIMESTAMP [(<seconds precision>)]
|
||||
|
||||
Type:
|
||||
TIME, TIMESTAMP
|
||||
|
||||
Scope:
|
||||
DSQL, PSQL
|
||||
|
||||
Example(s):
|
||||
1. SELECT CURRENT_TIME FROM RDB$DATABASE;
|
||||
2. SELECT CURRENT_TIME(3) FROM RDB$DATABASE;
|
||||
3. SELECT CURRENT_TIMESTAMP(3) FROM RDB$DATABASE;
|
||||
|
||||
Note(s):
|
||||
1. The maximum possible precision is 3 which means accuracy of 1/1000 second
|
||||
(one millisecond). This accurany may be improved in the future versions.
|
||||
2. If no seconds precision is specified, the following values are implicit:
|
||||
- 0 for CURRENT_TIME
|
||||
- 3 for CURRENT_TIMESTAMP
|
Loading…
Reference in New Issue
Block a user