ALTER DOMAIN Sample Clauses

ALTER DOMAIN. Changes a domain definition. Available in SQL, DSQL, and isql. Syntax ALTER DOMAIN name { [SET DEFAULT {literal | NULL | USER}] | [DROP DEFAULT] | [ADD [CONSTRAINT] CHECK (<dom_search_condition>)] | [DROP CONSTRAINT] }; Important In SQL statements passed to DSQL, omit the terminating semicolon. In embedded applications written in C and C++, and in isql, the semicolon is a terminating symbol for the statement, so it must be included. <dom_search_condition> = { VALUE <operator> <val> | VALUE [NOT] BETWEEN <val> AND <val> | VALUE [NOT] LIKE <val> [ESCAPE <val>] | VALUE [NOT] IN (<val> [, <val> ...]) | VALUE IS [NOT] NULL | VALUE [NOT] CONTAINING <val> | VALUE [NOT] STARTING [WITH] <val> | (<dom_search_condition>) | NOT <dom_search_condition> | <dom_search_condition> OR <dom_search_condition> | <dom_search_condition> AND <dom_search_condition> } SET DEFAULT Specifies a default column value that is entered when no other entry is made. Values: • literal—Inserts a specified string, numeric value, or date value. • NULL—Enters a NULL value. • USER—Enters the user name of the current user. Col- umn must be of compatible text type to use the default. Defaults set at column level override defaults set at the domain level. DROP DEFAULT Drops existing default. ADD [CONSTRAINT] CHECK Adds a CHECK constraint to the domain definition. A domain definition can include only one CHECK constraint. DROP CONSTRAINT Drops CHECK constraint from the domain definition. A domain can be altered by its creator, the SYSDBA user, and any users with operating system root privileges. Example The following isql statements create a domain that must have a value > 1,000, then alter it by setting a default of 9,999: CREATE DOMAIN CUSTNO AS INTEGER CHECK (VALUE > 1000); ALTER DOMAIN CUSTNO SET DEFAULT 9999; For a complete discussion of creating domains, and using them to create column definitions, see the Data Definition Guide. Changes the message associated with an existing exception. Available in DSQL and isql. Syntax ALTER EXCEPTION name "<message>" name Name of an existing exception message. "<message>" Quoted string containing ASCII values. An exception can be altered by its creator, the SYSDBA user, and any users with operating system root privileges. Example This isql statement alters the message of an exception: ALTER EXCEPTION CUSTOMER_CHECK "Hold shipment for customer remittance."; For more information on creating, raising, and handling exceptions, see the Data Definition Guide. Activa...
View Source
ALTER DOMAIN. This data structure will be used to make changes to the domain information. All fields, including the domain name itself, can be changed by the user. All demographic fields will be overwritten with the new values, so care must be taken to fill fields with all values, even the ones that have not changed. struct T_DOMAIN_EDIT{ struct T_DOMAIN Domain; char szNewDomainName[32]; int bRegisterDomain; char szNewUserName[32]; int bPasswordChanged; char szNewPassword[16]; }; The usage of the fields is as follows. nCOMMAND: CMD_ALTER. eSERVERTYPE: SERVER_DOMAIN. szDOMAINNAME: Old domain name. szUSERNAME: Old user name. szPASSWORD: Old password. szNEWDOMAINNAME: New domain name. If old and new domain names are the same, no domain name changes are made. This field is filled on input. bREGISTERDOMAIN: Defines whether domain should be registered or not. This permits users to move the account to a domain registered through some other means. No DNS server checks will be made while changing the domain name. This field is filled on input. szNEWUSERNAME: New Admin user name. If old and new admin user names are the same, no user account changes are made. This field is filled on input. szNEWPASSWORD: Holds the new password for the admin user account. This field is filled on input.
View Source

Related to ALTER DOMAIN

  • Public Domain if at the time of receipt by the party the Confidential Information is in the public domain or if, after the time of receipt by either party, the Confidential Information enters the public domain (except where it does so as a result of a breach by either party of its obligations under this clause 20 or a breach by any other person of that person’s obligation of confidence);

  • Contractor Designation of Trade Secrets or Otherwise Confidential Information If the Contractor considers any portion of materials to be trade secret under section 688.002 or 812.081, F.S., or otherwise confidential under Florida or federal law, the Contractor must clearly designate that portion of the materials as trade secret or otherwise confidential when submitted to the Department. The Contractor will be responsible for responding to and resolving all claims for access to Contract-related materials it has designated trade secret or otherwise confidential.

  • Trade Secrets and Proprietary Information (a) Executive recognizes and acknowledges that the Company, through the expenditure of considerable time and money, has developed and will continue to develop in the future information concerning customers, clients, marketing, products, services, business, research and development activities and operational methods of the Company and its customers or clients, contracts, financial or other data, technical data or any other confidential or proprietary information possessed, owned or used by the Company, the disclosure of which could or does have a material adverse effect on the Company, its business, any business it proposes to engage in, its operations, financial condition or prospects and that the same are confidential and proprietary and considered “confidential information” of the Company for the purposes of this Agreement. In consideration of his employment, Executive agrees that he will not, during or after the Term, without the consent of the Board make any disclosure of confidential information now or hereafter possessed by the Company, to any person, partnership, corporation or entity either during or after the term here of, except that nothing in this Agreement shall be construed to prohibit Executive from using or disclosing such information (a) if such disclosure is necessary in the normal course of the Company’s business in accordance with Company policies or instructions or authorization from the Board, (b) such information shall become public knowledge other than by or as a result of disclosure by a person not having a right to make such disclosure, or (c) subsequent to the Term, if such information shall have either (i) been developed by Executive independent of any of the Company’s confidential or proprietary information or (ii) been disclosed to Executive by a person not subject to a confidentiality agreement with or other obligation of confidentiality to the Company. For the purposes of Sections 6, 7 and 8 of this Agreement, the term “Company” shall include the Company, its parent, its subsidiaries and affiliates, other than affiliates whose relationship as an affiliate is derived solely from Executive’s interest in or position at the affiliate. (b) In the event that any trade secrets or other confidential information covered by Section 6(a) of this Agreement is required to be produced by Executive pursuant to legal process, Executive shall give the Company notice of such legal process within a reasonable time, but not later than ten (10) business days prior to the date such disclosure is to be made, unless Executive has received less notice, in which event Executive shall immediately notify the Company. The Company shall have the right to object to any such disclosure, and if the Company objects (at the Company’s cost and expense) in a timely manner so that Executive is not subject to penalties for failure to make such disclosure, Executive shall not make any disclosure until there has been a court determination on the Company’s objections. If disclosure is required by a court order, final beyond right of review, or if the Company does not object to the disclosure, Executive shall make disclosure only to the extent that disclosure is unequivocally required by the court order, and Executive will exercise reasonable efforts at the Company’s expense, to obtain reliable assurance that confidential treatment will be accorded the Confidential Information.

  • Ownership of Software and Related Material All computer programs, magnetic tapes, written procedures, and similar items purchased and/or developed and used by Price Associates in performance of this Agreement shall be the property of Price Associates and will not become the property of the Funds.

  • Confidential or Proprietary Information The term “Confidential or Proprietary Information” for purposes of this Agreement shall mean any secret, confidential, or proprietary information of SunTrust or a SunTrust Affiliate (not otherwise included in the definition of Trade Secret in § 1.20 of this Agreement) that has not become generally available to the public by the act of one who has the right to disclose such information without violating any right of SunTrust or a SunTrust Affiliate.