UPCASE (JANUS DEFINE parameter): Difference between revisions
m (1 revision) |
m (remove displaytitle) |
||
| (16 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle">Convert client "names" to uppercase</span> | |||
<span class="pageSubtitle" | |||
UPCASE is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port | <var>UPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for OPENSERV ports, column names for SDS ports and header parameters, header values, cookie names, and form field names for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. By setting UPCASE as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case. | This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for <var>[[JANUS DEFINE#type|OPENSERV]]</var> ports, column names for <var>[[JANUS DEFINE#type|SDS]]</var> ports and header parameters, header values, cookie names, and form field names for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. By setting <var>UPCASE</var> as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case. | ||
Note that it is possible to have lower case userids and passwords in | Note that it is possible to have lower case userids and passwords in <var class="product">Model 204</var>. For example, the userids <code>HOMER</code>, <code>homer</code>, and <code>Homer</code> would be treated as three separate userids by <var class="product">Model 204</var>. The <var>UPCASE</var> parameter simplifies the interaction between clients (where names tend to be in lowercase) and <var class="product">Model 204</var> (where they tend to be in uppercase). | ||
< | <p class="note">'''Note:''' The <var>UPCASE</var> parameter never results in data being converted to uppercase. That is, if a client sends variable <code>@customer</code> with a value of <code>Dolly Dinkle</code>, and <var>UPCASE</var> is active for the connection, the <var class="product">User Language</var> application would see a variable called <code>@CUSTOMER</code> with a value of <code>Dolly Dinkle</code>. </p> | ||
For SDS ports, the UPCASE parameter means that all table and column names passed from the Adaptive Server will be converted to | For <var>[[JANUS DEFINE#type|SDS]]</var> ports, the <var>UPCASE</var> parameter means that all table and column names passed from the Adaptive Server will be converted to uppercase. This means that when defining the columns and tables (using <var>[[JANCAT (JANUS DEFINE parameter)|JANCAT]]</var>), the names must all be uppercase. It also means that if an <var>SDS</var> port has the <var>UPCASE</var> parameter set but has mixed case table and column names, those tables and columns will be inaccessible. | ||
The UPCASE parameter is the opposite of <var>[[NOUPCASE (JANUS DEFINE parameter)|NOUPCASE]]</var>. The default is for all ports to have UPCASE set. | The <var>UPCASE</var> parameter is the opposite of <var>[[NOUPCASE (JANUS DEFINE parameter)|NOUPCASE]]</var>. The default is for all ports to have <var>UPCASE</var> set. | ||
Valid for <var> | Valid for <var>WEBSERV</var>, <var>OPENSERV</var> and <var>[[JANUS DEFINE#type|SDS]]</var> port types. | ||
==See also== | |||
<ul> | |||
<li>[[List of Janus commands]] | |||
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] | |||
</ul> | |||
[[Category:JANUS DEFINE parameters|UPCASE]] | [[Category:JANUS DEFINE parameters|UPCASE]] | ||
Latest revision as of 17:51, 27 January 2016
Convert client "names" to uppercase
UPCASE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for OPENSERV ports, column names for SDS ports and header parameters, header values, cookie names, and form field names for WEBSERV ports. By setting UPCASE as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case.
Note that it is possible to have lower case userids and passwords in Model 204. For example, the userids HOMER, homer, and Homer would be treated as three separate userids by Model 204. The UPCASE parameter simplifies the interaction between clients (where names tend to be in lowercase) and Model 204 (where they tend to be in uppercase).
Note: The UPCASE parameter never results in data being converted to uppercase. That is, if a client sends variable @customer with a value of Dolly Dinkle, and UPCASE is active for the connection, the User Language application would see a variable called @CUSTOMER with a value of Dolly Dinkle.
For SDS ports, the UPCASE parameter means that all table and column names passed from the Adaptive Server will be converted to uppercase. This means that when defining the columns and tables (using JANCAT), the names must all be uppercase. It also means that if an SDS port has the UPCASE parameter set but has mixed case table and column names, those tables and columns will be inaccessible.
The UPCASE parameter is the opposite of NOUPCASE. The default is for all ports to have UPCASE set.
Valid for WEBSERV, OPENSERV and SDS port types.