error when installing calypso (wp-calypso)

2015-11-26 KENNETH 7

error when installing wp-calypso   출처 : https://github.com/Automattic/wp-calypso/blob/master/docs/install.md   1. 소개된 설치법 사전설정 Check that you have all prerequisites (Git, Node, NPM). See below for more details. Clone this repository locally. Add 127.0.0.1 calypso.localhost to your local hosts file. Execute make run from the directory of the repository. Open calypso.localhost:3000 in your browser.   설치 $ git clone [email protected]:Automattic/wp-calypso.git $ cd wp-calypso $ make run     2. 오류.. # git clone [email protected]:Automattic/wp-calypso.git Cloning into ‘wp-calypso’… Warning: Permanently added the RSA host key for IP address ‘192.30.252.129’ to the list of known hosts. Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.   3. git 수행시 수정해줘야함 git clone https://github.com/Automattic/wp-calypso.git  

mariadb-10.0 mysqldump bug

2015-11-24 KENNETH 1

mysqldump bug on MariaDB 10.0   환경 OS : CentOS-6.7 (64bit) DB : MariaDB-10.0.21 / 설치형태 : 소스컴파일   내용 같은문자열을 가졌으나 문자열중 대/소문자를 구분하는 테이블들이 존재할 경우 mysqldump 를 이용한 백업시 ”CREATE TABLE”구문에 사용되는 테이블명이 중복되는 문제 (말로 푸는것이 어려우니 아래 내용을 봅시다)   예시 1. DB정보 db name : test table name : AbDc aBDc aBdc abdC   2. 테이블생성 mysql (test)> create table abdC (kk int(3), kk2 text); mysql (test)> create table aBdc (kk int(3), kk2 text); mysql (test)> create table aBDc (kk int(3), kk2 text); mysql (test)> create table AbDc (kk int(3), kk2 text);   3. DUMP mysqldump -uroot test AbDc > AbDc.sql mysqldump -uroot test aBDc > aBDc.sql mysqldump -uroot test aBdc > aBdc.sql mysqldump -uroot test abdC > abdC.sql   4. 백업 데이터 확인 # grep CREATE *.sql AbDc.sql:CREATE TABLE `AbDc` ( aBDc.sql:CREATE TABLE [ more… ]

error 1062 (23000) at line duplicate entry for key ‘primary’

2015-11-23 KENNETH 1

error 1062 (23000) at line XX duplicate entry for key ’primary’ 에 대한 고찰   데이터 마이그레이션 작업을 하면서 자꾸만 오류가 발생.. ERROR 1062 (23000) at line 23: Duplicate entry ‘4’ for key ‘PRIMARY’   운영중인 데이터베이스의 레코드와 해당 레코드를 DUMP한 내용을 아무리 살펴봐도 잘못된점을 찾을 수 없는 상황이었는데….   알고보니.. 동일한 테이블명이 존재하고 있었던것!!!!! ?????? 이런식으로.. -rw-rw—- 1 mysql mysql 462 Nov 23 17:57 abc.frm -rw-rw—- 1 mysql mysql 462 Nov 23 17:57 Abc.frm -rw-rw—- 1 mysql mysql 8192 Nov 23 17:57 abc.MAD -rw-rw—- 1 mysql mysql 8192 Nov 23 17:57 Abc.MAD -rw-rw—- 1 mysql mysql 8192 Nov 23 17:57 abc.MAI -rw-rw—- 1 mysql mysql 8192 Nov 23 17:57 Abc.MAI   물론 여기에 기재한것은 내가 테스트를 해본것이고.. 실제 이름은 다른거;;; ㅋ   만들어 보니까 정말로 저렇게 되더라고.. mysql (test)>create table abc (kk int(3), kk2 text); Query OK, 0 rows [ more… ]

mariadb supported engines

2015-11-18 KENNETH 0

출처 : https://mariadb.com/kb/en/mariadb/choosing-the-right-storage-engine/ 출처2 : https://mariadb.com/kb/en/mariadb/storage-engines/   MariaDB supported engines   The Archive storage engine is, unsurprisingly, best used for archiving. Aria, MariaDB’s more modern improvement on MyISAM, has a small footprint and allows for easy copy between systems. The BLACKHOLE storage engine accepts data but does not store it and always returns an empty result, useful, for example, if you want to run complex filtering rules on a slave without incurring any overhead on a master. Cassandra is a NoSQL engine. CONNECT allows access to different kinds of text files and remote resources as if they were regular MariaDB tables. The CSV storage engine can read and append to files stored in CSV (comma-separated-values) format. However, since MariaDB 10.0, CONNECT is a better storage engine is able to read and write such files. FederatedX uses libmysql to talk to the data [ more… ]

MySQL 5.7 Supported Storage Engines

2015-11-18 KENNETH 0

출처 : https://dev.mysql.com/doc/refman/5.7/en/storage-engines.html   MySQL 5.7 Supported Storage Engines InnoDB: The default storage engine in MySQL 5.7. InnoDB is a transaction-safe (ACID compliant) storage engine for MySQL that has commit, rollback, and crash-recovery capabilities to protect user data. InnoDB row-level locking (without escalation to coarser granularity locks) and Oracle-style consistent nonlocking reads increase multi-user concurrency and performance. InnoDB stores user data in clustered indexes to reduce I/O for common queries based on primary keys. To maintain data integrity, InnoDB also supports FOREIGN KEY referential-integrity constraints. For more information about InnoDB, see Chapter 14, The InnoDB Storage Engine. MyISAM: These tables have a small footprint. Table-level locking limits the performance in read/write workloads, so it is often used in read-only or read-mostly workloads in Web and data warehousing configurations. Memory: Stores all data in RAM, for fast access in environments that require [ more… ]