한국어

네트워킹

온누리070 플레이스토어 다운로드
    acrobits softphone
     온누리 070 카카오 프러스 친구추가온누리 070 카카오 프러스 친구추가친추
     카카오톡 채팅 상담 카카오톡 채팅 상담카톡
    
     라인상담
     라인으로 공유

     페북공유

   ◎위챗 : speedseoul


  
     PAYPAL
     
     PRICE
     

pixel.gif

    before pay call 0088 from app


https://mariadb.com/kb/en/the-mariadb-library/create-user/


CREATE [OR REPLACE] USER [IF NOT EXISTS] 
 user_specification [,user_specification] ...
  [REQUIRE {NONE | tls_option [[AND] tls_option] ...}]
  [WITH resource_option [resource_option] ...]

user_specification:
  username [authentication_option]

authentication_option:
  IDENTIFIED BY 'authentication_string' 
  | IDENTIFIED BY PASSWORD 'hash_string'
  | IDENTIFIED {VIA|WITH} authentication_plugin
  | IDENTIFIED {VIA|WITH} authentication_plugin BY 'authentication_string'
  | IDENTIFIED {VIA|WITH} authentication_plugin {USING|AS} 'hash_string'

tls_option:
  SSL 
  | X509
  | CIPHER 'cipher'
  | ISSUER 'issuer'
  | SUBJECT 'subject'

resource_option:
  MAX_QUERIES_PER_HOUR count
  | MAX_UPDATE_PER_HOUR count
  | MAX_CONNECTIONS_PER_HOUR count
  | MAX_USER_CONNECTIONS count

Description

The CREATE USER statement creates new MariaDB accounts. To use it, you must have the global CREATE USER privilege or the INSERT privilege for the mysql database. For each account, CREATE USER creates a new row in the mysql.user table that has no privileges.

See Account Names below for details on how account names are specified.

If any of the specified user accounts already exist, ERROR 1396 (HY000)results. If an error occurs, CREATE USER will still create the accounts that do not result in an error. Only one error is produced for all users which have not been created:

ERROR 1396 (HY000): 
  Operation CREATE USER failed for 'u1'@'%','u2'@'%'

Failed CREATE or DROP operations, for both users and roles, produce the same error code.

The account can be given a password with the optional IDENTIFIED BY clause. To specify the password in plain text, omit the PASSWORD keyword. To specify the password as the hashed value as returned by the PASSWORD function, include the PASSWORD keyword.

If you do not specify a password with the IDENTIFIED BY clause, the user will be able to connect without a password. A blank password is not a wildcard to match any password. The user must connect without providing a password if no password is set.

If you specify a plugin using the VIA clause, the plugin name must be an active authentication plugin as per show plugins. If it doesn't show up you will need to install it with INSTALL PLUGIN or install-soname). Some plugins require a plugin_option (like mysql_native_password).

OR REPLACE

MariaDB starting with 10.1.3

If the optional OR REPLACE clause is used, it acts as a shortcut for:

DROP USER IF EXISTS name;
CREATE USER name ...;

IF NOT EXISTS

MariaDB starting with 10.1.3

When the IF NOT EXISTS clause is used, MariaDB will return a warning instead of an error if the specified user already exists.

MAX_*_PER_HOUR

MariaDB starting with 10.2.0

Limit to the number of queries, updates or connections the user can place or make per hour. The query count excludes results returned from the query cache. If set to zero, the default, no limit is imposed.

MAX_USER_CONNECTIONS

MariaDB starting with 10.2.0

Limit to the number of simultaneous connections that the user can hold. If set to zero, the default, no limit is imposed.

tls_options

MariaDB starting with 10.2.0

MariaDB 10.2.0 introduced a number of tls options.

SSL

Specifies that the server will only permit encrypted TLS connections for the user.

X509

Requires the client to have a valid certificate whose signature can be verified with one of the CA certificates, although the issuer, subject and exact certificate are not checked. Implies encryption, so there's no need for the SSL option.

ISSUER

Requires the client to have a valid certificate issued by the specified issuer. Implies encryption, so there's no need for the SSL option. The client must specify the --ssl-key and --ssl-cert options to connect, and it is also recommended that the --ssl-ca option be specified in order to verify the server's public certificate.

SUBJECT

Requires the client to have a valid certificate with the specified subject. Implies encryption, so there's no need for the SSL option. The client must specify the --ssl-key and --ssl-cert options to connect, and it is also recommended that the --ssl-ca option be specified in order to verify the server's public certificate.

CIPHER

Specifies that a specific cipher method is used for encrypting connections.

Account Names

Account names have both a user name and a host name, and are specified as 'user_name'@'host_name'.

When you connect to a MariaDB server, your user name and host must match a single account.

The user name and host name may be unquoted, quoted as strings using double quotes (") or single quotes ('), or quoted as identifiers using backticks (`). You must use quotes when using special characters (such as a hyphen) or wildcard characters. If you quote, you must quote the user name and host name separately (for example 'user_name'@'host_name').

Host Names

If the host name is not provided, it is assumed to be '%'.

Host names may contain the wildcard characters % and _. They are matched as if by the LIKE clause. If you need to use a wildcard character literally (for example, to match a domain name with an underscore), prefix the character with a backslash. See LIKE for more information on escaping wildcard characters.

Host name matches are case-insensitive. Host names can match either domain names or IP addresses. Use 'localhost' as the host name to allow only local client connections.

You can use a netmask to match a range of IP addresses using 'base_ip/netmask' as the host name. A user with an IP address ip_addr will be allowed to connect if the following condition is true:

ip_addr & netmask = base_ip

You can only use netmasks that specify a multiple of 8 bits of the address to match. That is, only the following netmasks are allowed:

255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.255

Using 255.255.255.255 is equivalent to not using a netmask at all.

User Names

User names must match exactly, including case. You can use the empty string to allow a user with any user name.

It is possible for more than one account to match when a user connects. MariaDB selects the first matching account after sorting according to the following criteria:

  • Accounts with an exact host name are sorted before accounts using a wildcard in the host name. Host names using a netmask are considered to be exact for sorting.
  • Accounts with a wildcard in the host name are sorted according to the position of the first wildcard character. Those with a wildcard character later in the host name sort before those with a wildcard character earlier in the host name.
  • Accounts with a non-empty user name sort before accounts with an empty user name.

The following table shows a list of example account as sorted by these criteria:

+---------+-------------+
| User    | Host        |
+---------+-------------+
| joffrey | 192.168.0.3 |
|         | 192.168.0.% |
| joffrey | 192.168.%   |
|         | 192.168.%   |
+---------+-------------+

Once connected, you only have the privileges granted to the account that matched, not all accounts that could have matched. For example, consider the following commands:

CREATE USER 'joffrey'@'192.168.0.3';
CREATE USER 'joffrey'@'%';
GRANT SELECT ON test.t1 to 'joffrey'@'192.168.0.3';
GRANT SELECT ON test.t2 to 'joffrey'@'%';

If you connect as joffrey from 192.168.0.3, you will have the SELECT privilege on the table test.t1, but not on the table test.t2. If you connect as joffrey from any other IP address, you will have the SELECT privilege on the table test.t2, but not on the table test.t1.

MariaDB starting with 5.5.31

Beginning with MariaDB 5.5.31, usernames can be up to 80 characters long. However, in order to enable this feature, the following schema changes must be made:

alter table mysql.user         modify User         char(80)  binary not null default '';
alter table mysql.db           modify User         char(80)  binary not null default '';
alter table mysql.tables_priv  modify User         char(80)  binary not null default '';
alter table mysql.columns_priv modify User         char(80)  binary not null default '';
alter table mysql.procs_priv   modify User         char(80)  binary not null default '';
alter table mysql.proc         modify definer      char(141) collate utf8_bin not null default '';
alter table mysql.event        modify definer      char(141) collate utf8_bin not null default '';
alter table mysql.proxies_priv modify User         char(80)  COLLATE utf8_bin not null default '';
alter table mysql.proxies_priv modify Proxied_user char(80)  COLLATE utf8_bin not null default '';
alter table mysql.proxies_priv modify Grantor      char(141) COLLATE utf8_bin not null default '';
alter table mysql.servers      modify Username     char(80)                   not null default '';
alter table mysql.procs_priv   modify Grantor      char(141) COLLATE utf8_bin not null default '';
alter table mysql.tables_priv  modify Grantor      char(141) COLLATE utf8_bin not null default '';

flush privileges;

Examples

CREATE USER foo2@test IDENTIFIED BY 'password';

tls options, from MariaDB 10.2.0:

CREATE USER 'foo4'@'test' 
  REQUIRE ISSUER 'foo_issuer' 
  SUBJECT 'foo_subject' 
  CIPHER 'text'

Resource limits, from MariaDB 10.2.0

CREATE USER foo 
  WITH MAX_QUERIES_PER_HOUR 10
  MAX_UPDATES_PER_HOUR 20
  MAX_CONNECTIONS_PER_HOUR 30
  MAX_USER_CONNECTIONS 40;

OR REPLACE and IF NOT EXISTS:

CREATE USER foo2@test IDENTIFIED BY 'password';
ERROR 1396 (HY000): Operation CREATE USER failed for 'foo2'@'test'

CREATE OR REPLACE USER foo2@test IDENTIFIED BY 'password';
Query OK, 0 rows affected (0.00 sec)

CREATE USER IF NOT EXISTS foo2@test IDENTIFIED BY 'password';
Query OK, 0 rows affected, 1 warning (0.00 sec)

SHOW WARNINGS;
+-------+------+----------------------------------------------------+
| Level | Code | Message                                            |
+-------+------+----------------------------------------------------+
| Note  | 1973 | Can't create user 'foo2'@'test'; it already exists |
+-------+------+----------------------------------------------------+
1 row in set (0.00 sec

See also

조회 수 :
15729
등록일 :
2017.09.01
08:41:14 (*.160.88.18)
엮인글 :
http://webs.co.kr/index.php?document_srl=3311499&act=trackback&key=2fb
게시글 주소 :
http://webs.co.kr/index.php?document_srl=3311499
List of Articles
번호 제목 글쓴이 날짜 조회 수
65 [SQL] 테이블 안의 컬럼 값 변경, 수정, UPDATE admin 2019-10-21 16
64 [Android] 안드로이드 - SQLiteDatabase 구현하기 admin 2019-10-14 22
63 [유용][실전]Android DB 생성 및 관리 ( Cursor , Query ) 리스트뷰 admin 2019-10-14 15
62 간단한 Android Sqlite 예제 ( DB생성,테이블 생성, 데이터 입력, 테이터 보여주기) admin 2019-10-14 16
61 [안드로이드] SQLiteDatabase와 SQLiteOpenHelper 사용법 예제 admin 2019-10-14 19
60 두테이블비교 한쪽에 없는 값 추출 mysql left right outer join 서브쿼리 값사용 admin 2019-07-10 350
59 원격 IP로 MySQL(MariaDB)에 접속 방법 해법 설정 순서 admin 2019-06-19 402
58 oracle download install 오라클 다운로드 설치 admin 2018-05-29 3415
57 숫자 날짜 문자열 문자 공간 JSON MySQL 자료형 총 정리 phpMyAdmin 자료형 admin 2018-03-26 4185
56 mysql procedure admin 2017-11-16 4816
55 Sqlite very detail easy tutorial I recommand this admin 2017-09-09 6172
54 mysql 로컬접속 풀고 특정 아이피 접속 허가 허락 가능 하게 설정 하는 방법 admin 2017-09-05 5731
53 linux command chmod 리눅스 명령어 가장 쉽게 이해하기 설명 사용자 구룹 타인 권한 admin 2017-09-05 5912
» mariadb CREATE USER CREATE USER statement creates new MariaDB accounts. admin 2017-09-01 15729
51 MySQL 데이터 베이스 백업 및 복구 방법 admin 2017-09-01 6002
50 Allowing MySQL Root Login from All IP Addresses : admin 2017-08-17 5619
49 Installation of MySQL Database Server admin 2017-08-17 5565
48 mysql 쿼리 로그 남기기 (실시간) admin 2015-04-15 9730
47 SQL Delete records using subqueries admin 2015-04-03 8765
46 Mysql privilege table GRANT SELECT,INSERT,UPDATE,DELETE ON db.table admin 2015-04-02 8914
45 안드로이드 SQLite 속도 향상! insert Transaction admin 2014-04-07 23987
44 MySQL에 원격 접속 허용 여러가지 아이피 아이피대역으로 admin 2014-04-02 39804
43 10gR2_sles10_install file admin 2014-03-18 15855
42 this is final answer assets sqlite Databases trouble copy External DB, check eclips admin 2014-02-18 15965
41 Browse SQLite data on the Android emulator admin 2014-02-15 18340
40 SQLite Database Browser file admin 2014-02-14 17246
39 SQLite Databases using External DB admin 2014-02-14 19168
38 sqlite DB copy admin 2014-02-14 16056
37 Android SQLite Database with Multiple Tables admin 2014-02-13 13105
36 Android Simple Clean Good SQLite Database Tutorial 잘된 설명 admin 2014-02-13 14023