| select current_timestamp(3) |
[링크 : https://stackoverflow.com/questions/9624284/current-timestamp-in-milliseconds]
| NOW([precision]) CURRENT_TIMESTAMP CURRENT_TIMESTAMP([precision]) LOCALTIME, LOCALTIME([precision]) LOCALTIMESTAMP LOCALTIMESTAMP([precision]) |
| mariadb 초기설정 (0) | 2022.08.30 |
|---|---|
| mariadb c# connector (0) | 2021.10.22 |
| HeidiSQL (2) | 2021.08.18 |
| sql zerofill (0) | 2019.11.25 |
| mysql-dump compatible 함정 -_- (0) | 2019.09.04 |
어쩐지(?) mariadb 설치시 암호를 안물어 본다고 했더니
저런 이상한(?) 스크립트를 추가해놓은 듯.
| $ sudo mysql_secure_installation NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY! In order to log into MariaDB to secure it, we'll need the current password for the root user. If you've just installed MariaDB, and haven't set the root password yet, you should just press enter here. Enter current password for root (enter for none): OK, successfully used password, moving on... Setting the root password or using the unix_socket ensures that nobody can log into the MariaDB root user without the proper authorisation. You already have your root account protected, so you can safely answer 'n'. Switch to unix_socket authentication [Y/n] Enabled successfully! Reloading privilege tables.. ... Success! You already have your root account protected, so you can safely answer 'n'. Change the root password? [Y/n] New password: Re-enter new password: Password updated successfully! Reloading privilege tables.. ... Success! By default, a MariaDB installation has an anonymous user, allowing anyone to log into MariaDB without having to have a user account created for them. This is intended only for testing, and to make the installation go a bit smoother. You should remove them before moving into a production environment. Remove anonymous users? [Y/n] ... Success! Normally, root should only be allowed to connect from 'localhost'. This ensures that someone cannot guess at the root password from the network. Disallow root login remotely? [Y/n] y ... Success! By default, MariaDB comes with a database named 'test' that anyone can access. This is also intended only for testing, and should be removed before moving into a production environment. Remove test database and access to it? [Y/n] y - Dropping test database... ... Success! - Removing privileges on test database... ... Success! Reloading the privilege tables will ensure that all changes made so far will take effect immediately. Reload privilege tables now? [Y/n] y ... Success! Cleaning up... All done! If you've completed all of the above steps, your MariaDB installation should now be secure. Thanks for using MariaDB! |
| mariadb msec 단위 시간 얻기 (0) | 2022.08.31 |
|---|---|
| mariadb c# connector (0) | 2021.10.22 |
| HeidiSQL (2) | 2021.08.18 |
| sql zerofill (0) | 2019.11.25 |
| mysql-dump compatible 함정 -_- (0) | 2019.09.04 |
mysql, mariadb, amazon aurora, azure database for mysql을 지원하는 connector
MIT 라이선스를 적용하고 있고 다운로드 24.8M에 빛나는 패키지
[링크 : https://www.nuget.org/packages/MySqlConnector/1.3.14?_src=template]
mysql connector
[링크 : https://dev.mysql.com/downloads/connector/net/]
mariadb foundation의 connector는 소스로 제공되네..
| mariadb msec 단위 시간 얻기 (0) | 2022.08.31 |
|---|---|
| mariadb 초기설정 (0) | 2022.08.30 |
| HeidiSQL (2) | 2021.08.18 |
| sql zerofill (0) | 2019.11.25 |
| mysql-dump compatible 함정 -_- (0) | 2019.09.04 |
mariadb를 설치했더니 이런게 설치되서 찾아보는데..
mariadb / mssql / postgresql 를 지원한다!!
mariadb / postgresql은 ssh tunnel을 지원한다니 끌리네?
opensource / GPL
[링크 : https://www.heidisql.com/]
[링크 : https://www.heidisql.com/help.php#license]
| mariadb 초기설정 (0) | 2022.08.30 |
|---|---|
| mariadb c# connector (0) | 2021.10.22 |
| sql zerofill (0) | 2019.11.25 |
| mysql-dump compatible 함정 -_- (0) | 2019.09.04 |
| mysql / unix-socket (0) | 2019.09.04 |
[링크 : https://it.toolbox.com/question/padding-zeros-for-a-sequence-080714]
[링크 : https://stackoverflow.com/questions/6862766/how-to-create-postgresql-leading-zero-sequence-zerofill]
[링크 : https://w3resource.com/PostgreSQL/lpad-function.php]
[링크 : https://www.phpschool.com/gnuboard4/bbs/board.php?bo_table=qna_db&wr_id=131902]
+
mysql zerofill 이라는 옵션제공(table 생성시)
[링크 : https://m.blog.naver.com/luvtoma/221179414916]
단, 표시가 다르게 될 뿐이지, 실제 저장되는 데이터 사이즈가 달라지는건 아니라는 이야기
[링크 : https://www.phpschool.com/gnuboard4/bbs/board.php?bo_table=qna_db&wr_id=169515&page=638]
oracle에서는 LPAD나 RPAD혹은 TO_CHAR로 하라는거 봐서는
mysql에서만 제공하는 특수한 기능으로 보인다.
| mariadb c# connector (0) | 2021.10.22 |
|---|---|
| HeidiSQL (2) | 2021.08.18 |
| mysql-dump compatible 함정 -_- (0) | 2019.09.04 |
| mysql / unix-socket (0) | 2019.09.04 |
| mysql exists (0) | 2019.07.05 |
compatible을 넣는다고 해서 해당 compatible mode의 주석처리나 변수형이 바뀌진 않는다.. 인가?
|
Produce output that is more compatible with other database systems or with older MySQL servers. The value of name can be ansi, mysql323,mysql40, postgresql, oracle, mssql, db2, maxdb, no_key_options, no_table_options, or no_field_options. To use several values, separate them by commas. These values have the same meaning as the corresponding options for setting the server SQL mode. See Section 5.1.10, “Server SQL Modes”. This option does not guarantee compatibility with other servers. It only enables those SQL mode values that are currently available for making dump output more compatible. For example, --compatible=oracle does not map data types to Oracle types or use Oracle comment syntax. |
[링크 : https://dev.mysql.com/doc/refman/5.5/en/mysqldump.html]
[링크 : https://dev.mysql.com/doc/refman/5.5/en/sql-mode.html]
| HeidiSQL (2) | 2021.08.18 |
|---|---|
| sql zerofill (0) | 2019.11.25 |
| mysql / unix-socket (0) | 2019.09.04 |
| mysql exists (0) | 2019.07.05 |
| mysql timestamp 1분 이내 매치하기 (0) | 2018.12.21 |
그냥 root 권한은 유닉스 소켓으로 접속하게 되어있어서
sudo 를 통해 권한을 변경해서 접속하면 된다고... -_-
| $ sudo mysql -u root |
[링크 : https://stackoverflow.com/questions/39281594/error-1698-28000-access-denied-for-user-rootlocalhost]
| sql zerofill (0) | 2019.11.25 |
|---|---|
| mysql-dump compatible 함정 -_- (0) | 2019.09.04 |
| mysql exists (0) | 2019.07.05 |
| mysql timestamp 1분 이내 매치하기 (0) | 2018.12.21 |
| mysql join과 필드명 변경하기 (0) | 2018.12.21 |
| mysql-dump compatible 함정 -_- (0) | 2019.09.04 |
|---|---|
| mysql / unix-socket (0) | 2019.09.04 |
| mysql timestamp 1분 이내 매치하기 (0) | 2018.12.21 |
| mysql join과 필드명 변경하기 (0) | 2018.12.21 |
| join은 위험한 동물이다(?) (0) | 2018.12.21 |
between 이나 TIMEDIFF 이런걸로 될 줄 알았는데 영안되서
결국에는 +-15로 계산을 해야겠네.. 끄응
select T.temperature, T.humidity, T.created as tcreated, P.ph, P.voltage, P.created as pcreated from (select * from dht11 where DATE(created) >= '2018-12-20' ) as T, (select * from ph where DATE(created) >= '2018-12-20' ) as P WHERE TIME_TO_SEC(P.created) - 15 < TIME_TO_SEC(T.created) AND TIME_TO_SEC(T.created) < TIME_TO_SEC(P.created) + 15; |
[링크 : https://www.w3resource.com/mysql/date-and-time-functions/mysql-time_to_sec-function.php]
[링크 : https://stackoverflow.com/questions/7636599/calculating-time-difference-between-2-dates-in-minutes]
[링크 : https://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_timestampdiff]
| mysql / unix-socket (0) | 2019.09.04 |
|---|---|
| mysql exists (0) | 2019.07.05 |
| mysql join과 필드명 변경하기 (0) | 2018.12.21 |
| join은 위험한 동물이다(?) (0) | 2018.12.21 |
| mysql client 다른 호스트 접속하기 (0) | 2018.12.20 |
필드명도 table.field AS newfilename 으로 하면 되네
[링크 : https://statkclee.github.io/sql-ecology-lesson/kr/03-sql-joins-aliases.html]
| mysql exists (0) | 2019.07.05 |
|---|---|
| mysql timestamp 1분 이내 매치하기 (0) | 2018.12.21 |
| join은 위험한 동물이다(?) (0) | 2018.12.21 |
| mysql client 다른 호스트 접속하기 (0) | 2018.12.20 |
| ubuntu 18.04 apparmor와 mysql 충돌 (0) | 2018.11.19 |
|
