diff --git a/doc/README.instsvc b/doc/README.instsvc index bb48cb637d..2fb2c3d27d 100644 --- a/doc/README.instsvc +++ b/doc/README.instsvc @@ -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 */ diff --git a/doc/sql.extensions/README.current_time b/doc/sql.extensions/README.current_time new file mode 100644 index 0000000000..62745fca7d --- /dev/null +++ b/doc/sql.extensions/README.current_time @@ -0,0 +1,28 @@ +---------------------------------- +CURRENT_TIME and CURRENT_TIMESTAMP +---------------------------------- + + Function: + Returns current server system time or date+time values. + + Syntax rules: + CURRENT_TIME [()] + CURRENT_TIMESTAMP [()] + + 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