-
Content Count
128 -
Joined
-
Last visited
-
Days Won
13 -
Feedback
100%
Posts posted by Dimitris
-
-
-
What is jQuery?
jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript.
A Brief Look
DOM Traversal and Manipulation
Get the
<button>
element with the class 'continue' and change its HTML to 'Next Step...'1$( "button.continue" ).html( "Next Step..." )
Event Handling
Show the
#banner-message
element that is hidden withdisplay:none
in its CSS when any button in#button-container
is clicked.1234var hiddenBox = $( "#banner-message" );
$( "#button-container button" ).on( "click", function( event ) {
hiddenBox.show();
});
Ajax
Call a local script on the server
/api/getWeather
with the query parameterzipcode=97201
and replace the element#weather-temp
's html with the returned text.123456789$.ajax({
url: "/api/getWeather",
data: {
zipcode: 97201
},
success: function( result ) {
$( "#weather-temp" ).html( "<strong>" + result + "</strong> degrees" );
}
});
-
engaging
- Enticing content discovery
- More content generation
- Engaging social functionality
- Streamlined photos & videos
easy
- Launch site in as little as 15 min.
- Easily customized page templates
- Extensive personalization
- Optimized mobile experience
robust
- Excellent moderation control
- Built-in SEO
- Strong security
- World-class support
cloud
- Easy, non-technical site admin
- Hardware & hosting provided
- All key functionality included
- Low cost and no commitment
-
Four ways we can help your business thrive.
Create engaged fans
Gives fans a place to gather and wax lyrical on your terms. Passionate fans, given the right environment, can propel your brand to new audiences.
Improve employee sharing
Unparalled discussion and information sharing capabilities means your employees can share information with less friction and better efficiency.
Reduce support overheads
When customers can find the answers they need from peers quickly and easily, their reliance on your support team is reduced - along with your costs.
Grow customer loyalty
Members who feel invested in your community will also feel invested in - and loyalty to - your brand. Word of mouth is the best recommendation around!
- 1
-
What's in 3.6.3
Joomla! 3.6.3 comes with more than 350 merged PR and small improvements in many areas. We have also updated the wysiwyg editors:
- TinyMCE to 4.4.3
- CodeMirror to 5.18.0
-
Τι είναι το WordPress
Το WordPress είναι ένα σύγχρονο σύστημα διαδικτυακών δημοσιεύσεων και διαχείρισης περιεχομένου· μ’ άλλα λόγια, ένα μέσο για να φτιάξετε έναν ιστότοπο (site) ή ιστολόγιο (blog) ωραία και απλά και να δημοσιεύετε κάθε είδους περιεχόμενο: άρθρα, σκέψεις, φωτογραφίες, βίντεο, πληροφορίες για προϊόντα και υπηρεσίες – ό,τι θέλετε!
Ο μόνος περιορισμός είναι η φαντασία σας
Το WordPress διατίθεται δωρεάν και είναι ελεύθερο λογισμικό ανοιχτού κώδικα.
-
Meet OpenCart: the free, open-source and easy to use ecommerce platform.
No monthly fees, no catches; just an effective and customisable platform for your new ecommerce store. Simply install, choose your template, add products and you’re ready to start accepting orders.
Stick with the modern, responsive default theme or choose from thousands of themes online to make your store unique and perfectly suited for your business.
OpenCart comes with a fully mobile friendly admin area, complete with detailed product, order and customer management, sales reports, marketing tools and even more - allowing you to manage every aspect of your new online store from any device, anywhere in the World. Use the quick and concise dashboard to keep track of your sales, or choose from one of the many menu options to view more detail.
With a huge range of features included out-of-the-box and over 14,000 additional extensions available to download, OpenCart is perfect for ecommerce stores of any size, any industry, any budget.
- Open Source
- Fully Customisable
- Easy to Follow Documentation
- Unlimited Categories
- Unlimited Products
- Unlimited Manufacturers
- Template System
- Multi-Language
- Multi-Currency
- Product Reviews & Ratings
- Downloadable Products
- PCI Compliant
- Over 40 Payment Gateways
- Integrated Fraud Modules
- Free to Download & Use
- Automatic Image Resizing
- Multiple Tax Rates
- Related Products
- Unlimited Information Pages
- Shipping Weight Calculation
- Discount Coupon System
- Search Engine Optimization (SEO)
- Module Installer
- Backup & Restore Tools
- Printable Invoices
- Sales Reports
- Error Logging
- & Much More
-
You're in creative control
PrestaShop includes an out-of-the-box theme so you can welcome customers the moment you set up. Easily customize the PrestaShop theme by changing fonts and colors with the Live Configurator.
Stand out with mobile-responsive design
Welcome visitors from anywhere at anytime with a mobile-optimized site. PrestaShop's default template displays beautifully across all screens, from desktop computers to smartphones to tablet devices.
2,000+ professional ecommerce website templates
Make a lasting impression with a beautiful template from PrestaShop Addons. No matter what your online business is, you'll find the perfect template waiting for you.
https://www.prestashop.com/en/download
- 1
-
Magento Community Edition
A Flexible, Open Source Commerce Platform
for Developers and Small Businesses -
Minor updates to our Certification Practice Statement (CPS) this week.
Changelog:
This update contains a small number of higher priority changes:
1) Do not require discontinuing use of a private key due to incorrect information in a certificate.
2) Add information about issuance for Internationalized Domain Names.
3) Add information about CA’s CAA identifying domain.
4) Do not require discontinuing use of a private key due to expiration or revocation of a certificate.
We've just posted an updated CPS document on our repository page:
-
csf 9.24
This suite of scripts provides:
- Straight-forward SPI iptables firewall script
-
Daemon process that checks for login authentication failures for:
- Courier imap, Dovecot, uw-imap, Kerio
- openSSH
- cPanel, WHM, Webmail (cPanel servers only)
- Pure-ftpd, vsftpd, Proftpd
- Password protected web pages (htpasswd)
- Mod_security failures (v1 and v2)
- Suhosin failures
- Exim SMTP AUTH
- Custom login failures with separate log file and regular expression matching
- POP3/IMAP login tracking to enforce logins per hour
- SSH login notification
- SU login notification
- Excessive connection blocking
- UI Integration for cPanel, DirectAdmin and Webmin
- Easy upgrade between versions from within cPanel/WHM, DirectAdmin or Webmin
- Easy upgrade between versions from shell
- Pre-configured to work on a cPanel server with all the standard cPanel ports open
- Pre-configured to work on a DirectAdmin server with all the standard DirectAdmin ports open
- Auto-configures the SSH port if it's non-standard on installation
- Block traffic on unused server IP addresses - helps reduce the risk to your server
- Alert when end-user scripts sending excessive emails per hour - for identifying spamming scripts
- Suspicious process reporting - reports potential exploits running on the server
- Excessive user processes reporting
- Excessive user process usage reporting and optional termination
- Suspicious file reporting - reports potential exploit files in /tmp and similar directories
- Directory and file watching - reports if a watched directory or a file changes
- Block traffic on a variety of Block Lists including DShield Block List and Spamhaus DROP List
- BOGON packet protection
- Pre-configured settings for Low, Medium or High firewall security (cPanel servers only)
- Works with multiple ethernet devices
- Server Security Check - Performs a basic security and settings check on the server (via cPanel/DirectAdmin/Webmin UI)
- Allow Dynamic DNS IP addresses - always allow your IP address even if it changes whenever you connect to the internet
- Alert sent if server load average remains high for a specified length of time
- mod_security log reporting (if installed)
- Email relay tracking - tracks all email sent through the server and issues alerts for excessive usage (cPanel servers only)
- IDS (Intrusion Detection System) - the last line of detection alerts you to changes to system and application binaries
- SYN Flood protection
- Ping of death protection
- Port Scan tracking and blocking
- Permanent and Temporary (with TTL) IP blocking
- Exploit checks
- Account modification tracking - sends alerts if an account entry is modified, e.g. if the password is changed or the login shell
- Shared syslog aware
- Messenger Service - Allows you to redirect connection requests from blocked IP addresses to preconfigured text and html pages to inform the visitor that they have been blocked in the firewall. This can be particularly useful for those with a large user base and help process support requests more efficiently
- Country Code blocking - Allows you to deny or allow access by ISO Country Code
- Port Flooding Detection - Per IP, per Port connection flooding detection and mitigation to help block DOS attacks
- DirectAdmin UI integration
- Updated Webmin UI integration
- WHM root access notification (cPanel servers only)
- lfd Clustering - allows IP address blocks to be automatically propagated around a group of servers running lfd. It allows allows cluster-wide allows, removals and configuration changes
- Quick start csf - deferred startup by lfd for servers with large block and/or allow lists
- Distributed Login Failure Attack detection
- Temporary IP allows (with TTL)
- IPv6 Support with ip6tables
- Integrated UI - no need for a separate Control Panel or Apache to use the csf configuration
- Integrated support for cse within the Integrated UI
- cPanel Reseller access to per reseller configurable options Unblock, Deny, Allow and Search IP address blocks
- System Statistics - Basic graphs showing the performance of the server, e.g. Load Averages, CPU Usage, Memory Usage, etc
- ipset support for large IP lists
- ...lots more!
The reason we have developed this suite is that we have found over the years of providing server services that many of the tools available for the task are either over-complex, not user friendly, or simply aren't as effective as they could be.
ConfigServer Firewall (csf)
We have developed an SPI iptables firewall that is comprehensive, straight-forward, easy and flexible to configure
Login Failure Daemon (lfd)
To complement the ConfigServer Firewall (csf), we have developed a Login Failure Daemon (lfd) process that runs all the time and periodically (every X seconds) scans the latest log file entries for login attempts against your server that continually fail within a short period of time. Such attempts are often called "Brute-force attacks" and the daemon process responds very quickly to such patterns and blocks offending IP's quickly. Other similar products run every x minutes via cron and as such often miss break-in attempts until after they've finished, our daemon eliminates such long waits and makes it much more effective at performing its task.
Login tracking is an extension of lfd, it keeps track of POP3 and IMAP logins and limits them to X connections per hour per account per IP address.
Control Panel Configuration Interface
To help with the ease and flexibility of the suite we have developed a front-end to both csf and lfd which is accessible by the root account through cPanel, DirectAdmin and Webmin. From there you can modify the configuration files and stop, start and restart the applications and check their status. This makes configuring and managing the firewall very simple indeed.
ChangeLog: 9.24 - UI html fixes 9.23 - Added upgrade note to the top of the UI if available UI improvements for integrated cse and interface to cxs Added Scroll to Top/Bottom buttons Consolidate images, css and javascript into a common directory in the installer
-
The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.18. This is a Stable (GA) release.
Notable Changes
- XtraDB updated to 5.6.32-78.1
- TokuDB updated to 5.6.32-78.1
- Innodb updated to 5.6.33
- Performance Schema updated to 5.6.33
- Optimizer sometimes use "index" instead of "range" access for UPDATE (MDEV-10649)
Changelog:
-
Revision #6925689 2016-09-29 14:58:32 -0400
- MDEV-9312: storage engine not enforced during galera cluster replication
-
Revision #235876d 2016-09-29 14:21:14 +0200
- update test results after merge
- Revision #2ede40e 2016-09-29 12:59:51 +0200 - Merge branch '10.0' into 10.1
- Revision #a3f11f7 2016-09-29 12:31:46 +0200 - Merge branch '5.5' into 10.0
-
Revision #7497ebf 2016-09-29 10:16:24 +0200
- mysqld_safe: close stdout and stderr
-
Revision #0e76054 2016-09-28 12:52:01 +0000
- Feedback plugin : add support for Windows 10 / Server 2016.
-
Revision #b38d3c3 2016-09-27 12:34:15 +0000
- MDEV-10907 MTR and server writes can interleave in the error log
-
Revision #ad20769 2016-09-29 11:50:13 +0200
- init plugin psi keys before LOCK_plugin
-
Revision #b34c813 2016-09-28 22:12:03 +0200
- MDEV-10201 SSL tests fail on fedora23
-
Revision #9ff9acb 2016-09-22 17:52:05 +0200
-
MDEV-10716: Assertion
`real_type() != FIELD_ITEM'
failed inItem_ref::build_equal_items(THD*, COND_EQUAL*, bool, COND_EQUAL)
-
MDEV-10716: Assertion
-
Revision #d5dfa0f 2016-09-28 13:27:34 -0400
- MDEV-9416: MariaDB galera got signal 11 when altering table add unique index
-
Revision #7c525ce 2016-09-28 13:26:13 -0400
- MDEV-9312: storage engine not enforced during galera cluster replication
-
Revision #88f2ec6 2016-09-28 13:23:31 -0400
- MDEV-10041: Server crashes sporadically during bootstrap while running wsrep tests
- Revision #e1c6f28 2016-09-28 13:20:02 -0400 - Merge branch '10.0-galera' into 10.1
-
Revision #c9ded85 2016-09-21 10:51:37 +0200
- MDEV-10853 netcat help output in error log when running xtrabackup SST
-
Revision #3dd88fb 2016-09-01 12:59:11 -0400
- MDEV-10714: Could not execute Delete_rows event on table; wsrep_max_ws_rows exceeded. Error_Code 1180
-
Revision #616271b 2016-09-01 12:53:44 -0400
- Cleanup: MDL_context::wsrep_get_thd() is no longer needed
-
Revision #16702ec 2016-08-25 21:19:25 -0400
- Record wsrep.variables test result (with non-debug galera library).
-
Revision #735a4a1 2016-09-28 17:59:11 +0200
- MDEV-10508 Mariadb crash on out of disk space during dump import
-
Revision #794c826 2016-09-26 14:29:23 +0200
- MDEV-10890 plugins.pam fails in buildbot with valgrind
- Revision #66d9696 2016-09-28 17:55:28 +0200 - Merge branch '10.0' into 10.1
- Revision #23af6f5 2016-09-28 16:19:58 +0300 - Merge branch '10.0' of github.com:MariaDB/server into 10.0
- Revision #078e510 2016-09-27 19:03:11 +0200 - Merge branch 'merge/merge-tokudb-5.6' into 10.0
-
Revision #e312e2e 2016-09-27 17:59:58 +0200
- 5.6.32-78.1
- Revision #2e914ac 2016-09-27 19:00:08 +0200 - Merge branch 'merge/merge-perfschema-5.6' into 10.0
-
Revision #e3124a8 2016-09-27 17:57:28 +0200
- 5.6.33
- Revision #bb8b658 2016-09-27 18:58:57 +0200 - Merge branch 'merge/merge-xtradb-5.6' into 10.0
-
Revision #93ab309 2016-09-27 18:00:59 +0200
- 5.6.32-78.1
- Revision #3629f62 2016-09-27 18:05:06 +0200 - Merge branch 'merge/merge-innodb-5.6' into 10.0
-
Revision #094f140 2016-09-27 17:56:00 +0200
- 5.6.33
- Revision #77ce4ea 2016-09-27 09:21:19 +0200 - Merge branch '5.5' into 10.0
-
Revision #d61e526 2016-09-26 17:48:08 +0200
- MDEV-10441 Document the server_audit_loc_info variable
-
Revision #c91fdb6 2016-09-26 13:03:02 +0200
- Windows , mtr : allow cdb to print core dumps also if --parallel > 1
-
Revision #8483659 2016-09-24 10:06:58 +0200
- report correct write error on log writes
-
Revision #f620da1 2016-09-24 01:17:35 +0200
- MDEV-10725 Server 10.1.17 fails to build using clang with c++11
-
Revision #9434431 2016-09-24 13:50:42 +0200
- Fix free() after my_malloc() (should be my_free()).
-
Revision #b3f7a80 2016-09-13 11:12:54 -0400
- bump the VERSION
-
Revision #0da39ca 2016-09-12 16:18:07 +0200
- fix BIGINT+MEDIUMINT type aggregation
-
Revision #347eeef 2016-09-11 20:55:11 +0200
- don't use my_copystat in the server
-
Revision #611dc0d 2016-09-11 20:53:16 +0200
- missing element in prelocked_mode_name[] array
-
Revision #a229091 2016-09-11 20:52:00 +0200
- potential signedness issue
- Revision #7ae555c 2016-09-11 20:51:09 +0200 - Merge branch 'mysql/5.5' into 5.5
-
Revision #b9631e3 2015-11-10 12:41:26 +0100
- MDEV-8833 Crash of server on prepared statement with conversion to semi-join
-
Revision #ee97274 2016-08-25 09:50:04 +0300
- DEV-10595 MariaDB daemon leaks memory with specific query
-
Revision #a92a8cc 2016-08-19 17:11:20 +0000
- Windows packaging : use /d switch to sign MSI, to prevent installer showing randomly generated name in UAC prompt
-
Revision #723488b 2016-08-04 15:43:52 +0400
-
MDEV-10424 - Assertion
`ticket == null'
failed in MDL_request::set_type
-
MDEV-10424 - Assertion
-
Revision #09cb646 2016-08-11 19:35:53 +0000
- Windows : fix search for WiX root directory when using 64bit cmake
-
Revision #737964d 2016-08-10 11:24:18 -0400
- bump the VERSION
-
Revision #677c44f 2016-09-23 20:27:58 +0200
- MDEV-10775 System table in InnoDB format allowed in MariaDB could lead to crash
-
Revision #e56a539 2016-07-01 13:57:18 +0400
- MDEV-10315 - Online ALTER TABLE may get stuck in tdc_remove_table
-
Revision #83d5b96 2016-09-19 17:15:18 +0200
- Fix tokudb jemalloc linking
-
Revision #fd0c114 2016-09-12 14:57:32 +0200
- Update contributors
-
Revision #6e02d42 2016-09-13 13:16:11 +0200
- Fix compilation failure of TokuDB on BSD-like systems
-
Revision #b34d7fb 2016-09-11 11:18:27 +0200
- Debian bug#837369 - test failures on hppa
-
Revision #af3dc48 2016-09-10 20:42:20 +0200
- Attempt to fix strange rpm dependency issue following prior patch
-
Revision #577f3c1 2016-09-10 17:50:32 +0200
- Fix use of `require` in mysql-test-run.
-
Revision #6c74ef8 2016-09-07 09:30:02 +1000
- MDEV-10707: Fix tokudb test rows-32m-rand-insert (#231)
-
Revision #a14f61e 2016-09-05 12:28:35 +0300
- MDEV-7142: main.index_merge_innodb fails sporadically in buildbot
-
Revision #f81f985 2016-08-29 11:53:33 +0200
- fix conpilation on OpenBSD
-
Revision #39ec5ac 2016-08-25 11:55:54 -0400
- bump the VERSION
- Revision #66a58f4 2016-09-28 16:19:05 +0300 - Merge fix for MDEV-10649 from 10.0 to 10.1
-
Revision #a53f3c6 2016-09-28 16:12:58 +0300
- MDEV-10649: Optimizer sometimes use "index" instead of "range" access for UPDATE
-
Revision #0e47223 2016-09-27 17:38:47 +0200
- Make sure to recompile the feedback plugin for EMBEDDED
-
Revision #e226276 2016-09-14 18:15:03 +0200
- MDEV-10777: Server crashed due to query_cache_info plugin
-
Revision #3f5aedc 2016-09-27 11:18:24 +0000
- MDEV-10847 Bring AWS KMS encryption plugin up-to-date with released SDK
-
Revision #f1aefd9 2016-09-23 18:55:44 +0200
- MDEV-10823 Certain unicode characters in hostname prevent mysqld from starting
-
Revision #661d08c 2016-09-26 15:16:00 +0300
- MDEV-10887: innodb.innodb_stats_fetch_nonexistent fails in buildbot on Windows
-
Revision #452e849 2016-09-26 12:29:31 +0300
- MDEV-10886: encryption.innodb-bad-key-change fails (crashes) in buildbot
-
Revision #4e2a0c3 2016-09-26 09:58:50 +0300
- MDEV-10888: encryption.filekeys_emptyfile fails in buildbot with valgrind
-
Revision #d30809a 2016-09-26 09:40:47 +0400
- MDEV-10832 Out of tree build: mysql_install_db to see all .sql files.
-
Revision #7d7b92c 2016-09-24 14:21:27 +0300
- Disable encryption info and first page read info for every tablespace on product builds.
-
Revision #5d001d1 2016-09-23 17:28:38 +1000
- MDEV-10832 - Out of tree build: mysql_install_db to see all .sql files (#237)
-
Revision #e136aa1 2016-09-23 09:11:11 +0300
- Fix test failure. Need to mask more tablespace numbers as they are not consistent on parallel mtr runs.
-
Revision #1d55cfc 2016-09-22 20:57:15 +0300
- Do not use os_file_read() directly for reading first page of the tablespace. Instead use fil_read() with syncronous setting. Fix test failures and mask tablespace number as it could change in concurrent mtr runs.
-
Revision #2bedc39 2016-09-22 16:32:26 +0300
- MDEV-9931: InnoDB reads first page of every .ibd file at startup
-
Revision #e387bfa 2016-09-22 19:14:40 +1000
- MDEV-10830 - Fix undefined database test error when running mysql_install_db (#234)
-
Revision #9f837c6 2016-09-22 10:03:12 +0400
- MDEV-10864 Wrong result for WHERE .. (f2=COMPRESS('test') OR f2=COMPRESS('TEST'))
-
Revision #7e4eb99 2016-09-22 07:00:10 +0400
-
MDEV-10425 Assertion
`collation.derivation == DERIVATION_IMPLICIT'
failed inItem_func_conv_charset::fix_length_and_dec()
-
MDEV-10850 Wrong result for
WHERE .. (f2=TO_BASE64('test') OR f2=TO_BASE64('TEST'))
-
MDEV-10425 Assertion
-
Revision #ec7e0b7 2016-09-21 09:13:33 +0400
-
MDEV-10556 Assertion
`0'
failed in virtual voidItem_sum_field::set_result_field(Field*)
-
MDEV-10556 Assertion
-
Revision #8b51bac 2016-09-20 21:32:53 -0400
- MDEV-10735: Valgrind warnings around Galera SST
-
Revision #6eca463 2016-09-20 15:17:57 -0400
- Fix typo in valgrind.supp
- Revision #bb2c1a5 2016-09-09 11:53:50 +0200 - Merge parallel replication async deadlock kill into 10.1
-
Revision #7e0c9de 2016-09-08 15:25:40 +0200
- Parallel replication async deadlock kill
-
Revision #de7f877 2016-09-09 08:40:24 +0400
- MDEV-10702 Crash in SET STATEMENT FOR EXECUTE
-
Revision #8494039 2016-09-06 16:34:25 +0200
- fix the test to work
-
Revision #61fd38a 2016-09-05 17:11:14 +0200
- update plugin maturities
-
Revision #362ad94 2016-09-05 09:11:42 +0200
- cleanup: don't copy-paste, don't current_thd
-
Revision #747893a 2016-09-02 14:40:09 -0400
- MDEV-10545: Update perfschema.nesting result
-
Revision #31697d0 2016-09-02 12:21:40 -0400
- MDEV-10545: Server crashed in my_copy_fix_mb on querying I_S and P_S tables
-
Revision #a322651 2016-08-29 16:44:46 +0200
- MDEV-10017: Get unexpected `Empty Set` for correlated subquery with aggregate functions
- Revision #f6e47c0 2016-08-31 11:51:12 +0400 - Merge pull request #224 from 0xAX/build-get-rid-from-die
-
Revision #080ac47 2016-08-25 15:56:53 +0600
- remove die() from BUILD/autorun.sh
-
Revision #64fe389 2016-08-30 10:32:37 -0400
- bump the VERSION
-
Percona Server 5.7 - Documentation
Percona Server is an enhanced drop-in replacement for MySQL. With Percona Server,
- Your queries will run faster and more consistently.
- You will consolidate servers on powerful hardware.
- You will delay sharding, or avoid it entirely.
- You will save money on hosting fees and power.
- You will spend less time tuning and administering.
- You will achieve higher uptime.
- You will troubleshoot without guesswork.
Does this sound too good to be true? It’s not. Percona Server offers breakthrough performance, scalability, features, and instrumentation. Its self-tuning algorithms and support for extremely high-performance hardware make it the clear choice for companies who demand the utmost performance and reliability from their database server.
-
Features Added in MySQL 5.7
The following features have been added to MySQL 5.7:
-
Security improvements. These security enhancements were added:
-
The server now requires account rows in the
mysql.user
table to have a nonemptyplugin
column value and disables accounts with an empty value. For server upgrade instructions, see Section 2.11.1.1, “Changes Affecting Upgrades to MySQL 5.7”. DBAs are advised to also convert accounts that use themysql_old_password
authentication plugin to usemysql_native_password
instead, because support formysql_old_password
has been removed. For account upgrade instructions, see Section 7.5.1.3, “Migrating Away from Pre-4.1 Password Hashing and the mysql_old_password Plugin”. -
MySQL now enables database administrators to establish a policy for automatic password expiration: Any user who connects to the server using an account for which the password is past its permitted lifetime must change the password. For more information, see Section 7.3.6, “Password Expiration Policy”.
-
Administrators can lock and unlock accounts for better control over who can log in. For more information, see Section 7.3.10, “User Account Locking”.
-
To make it easier to support secure connections, MySQL servers compiled using OpenSSL can automatically generate missing SSL and RSA certificate and key files at startup. See Section 7.4.6.1, “Creating SSL and RSA Certificates and Keys using MySQL”.
All servers (whether compiled using OpenSSL or yaSSL), if not configured for SSL explicitly, attempt to enable SSL automatically at startup if they find the requisite SSL files in the data directory. See Section 7.4.4, “Configuring MySQL to Use Secure Connections”.
In addition, MySQL distributions include a mysql_ssl_rsa_setup utility that can be invoked manually to create SSL and RSA key and certificate files. For more information, see Section 5.4.5, “mysql_ssl_rsa_setup — Create SSL/RSA Files”.
-
MySQL deployments installed using mysqld --initialize are secure by default. The following changes have been implemented as the default deployment characteristics:
-
The installation process creates only a single
root
account,'root'@'localhost'
, automatically generates a random password for this account, and marks the password expired. The MySQL administrator must connect asroot
using the random password and assign a new password. (The server writes the random password to the error log.) -
Installation creates no anonymous-user accounts.
-
Installation creates no
test
database.
For more information, see Section 2.10.1.1, “Initializing the Data Directory Manually Using mysqld”.
-
-
-
SQL mode changes. Strict SQL mode for transactional storage engines (
STRICT_TRANS_TABLES
) is now enabled by default.Implementation for the
ONLY_FULL_GROUP_BY
SQL mode has been made more sophisticated, to no longer reject deterministic queries that previously were rejected. In consequence, this mode is now enabled by default, to prohibit only nondeterministic queries containing expressions not guaranteed to be uniquely determined within a group.The
ERROR_FOR_DIVISION_BY_ZERO
,NO_ZERO_DATE
, andNO_ZERO_IN_DATE
SQL modes are now deprecated but enabled by default. The long term plan is to have them included in strict SQL mode and to remove them as explicit modes in a future MySQL release. See SQL Mode Changes in MySQL 5.7.The changes to the default SQL mode result in a default
sql_mode
system variable value with these modes enabled:ONLY_FULL_GROUP_BY
,STRICT_TRANS_TABLES
,NO_ZERO_IN_DATE
,NO_ZERO_DATE
,ERROR_FOR_DIVISION_BY_ZERO
,NO_AUTO_CREATE_USER
, andNO_ENGINE_SUBSTITUTION
. -
Online ALTER TABLE.
ALTER TABLE
now supports aRENAME INDEX
clause that renames an index. The change is made in place without a table-copy operation. It works for all storage engines. See Section 14.1.8, “ALTER TABLE Syntax”. -
ngram and MeCab full-text parser plugins. As of MySQL 5.7.6, MySQL provides a built-in full-text ngram parser plugin that supports Chinese, Japanese, and Korean (CJK), and an installable MeCab full-text parser plugin for Japanese.
For more information, see Section 13.9.8, “ngram Full-Text Parser”, and Section 13.9.9, “MeCab Full-Text Parser Plugin”.
-
InnoDB enhancements. These
InnoDB
enhancements were added:-
VARCHAR
size may be increased using an in-placeALTER TABLE
, as in this example:ALTER TABLE t1 ALGORITHM=INPLACE, CHANGE COLUMN c1 c1 VARCHAR(255);
This is true as long as the number of length bytes required by a
VARCHAR
column remains the same. ForVARCHAR
values of 0 to 255, one length byte is required to encode the value. ForVARCHAR
values of 256 bytes or more, two length bytes are required. As a result, in-placeALTER TABLE
only supports increasingVARCHAR
size from 0 to 255 bytes or increasingVARCHAR
size from a value equal to or greater than 256 bytes.In-place
ALTER TABLE
does not support increasingVARCHAR
size from less than 256 bytes to a value equal to or greater than 256 bytes. In this case, the number of required length bytes would change from 1 to 2, which is only supported by a table copy (ALGORITHM=COPY
). For example, attempting to changeVARCHAR
column size from 255 to 256 using in-placeALTER TABLE
would return an error:ALTER TABLE t1 ALGORITHM=INPLACE, CHANGE COLUMN c1 c1 VARCHAR(256); ERROR 0A000: ALGORITHM=INPLACE is not supported. Reason: Cannot change column type INPLACE. Try ALGORITHM=COPY.
Decreasing
VARCHAR
size using in-placeALTER TABLE
is not supported. DecreasingVARCHAR
size requires a table copy (ALGORITHM=COPY
). -
DDL performance for
InnoDB
temporary tables is improved through optimization ofCREATE TABLE
,DROP TABLE
,TRUNCATE TABLE
, andALTER TABLE
statements. -
InnoDB
temporary table metadata is no longer stored toInnoDB
system tables. Instead, a new table,INNODB_TEMP_TABLE_INFO
, provides users with a snapshot of active temporary tables. The table contains metadata and reports on all user and system-created temporary tables that are active within a givenInnoDB
instance. The table is created when the firstSELECT
statement is run against it. -
InnoDB
now supports MySQL-supported spatial data types. Prior to this release,InnoDB
would store spatial data as binaryBLOB
data.BLOB
remains the underlying data type but spatial data types are now mapped to a newInnoDB
internal data type,DATA_GEOMETRY
. -
There is now a separate tablespace for all non-compressed
InnoDB
temporary tables. The new tablespace is always recreated on server startup and is located inDATADIR
by default. A newly added configuration file option,innodb_temp_data_file_path
, allows for a user-defined temporary data file path. -
In MySQL 5.7.2, innochecksum functionality is enhanced with several new options and extended capabilities. See Section 5.6.1, “innochecksum — Offline InnoDB File Checksum Utility”.
-
A new type of non-redo undo log for both normal and compressed temporary tables and related objects now resides in the temporary tablespace. For more information, see Section 15.4.12.1, “InnoDB Temporary Table Undo Logs”.
-
In MySQL 5.7.2,
InnoDB
buffer pool dump and load operations are enhanced. A new system variable,innodb_buffer_pool_dump_pct
, allows you to specify the percentage of most recently used pages in each buffer pool to read out and dump. When there is other I/O activity being performed byInnoDB
background tasks,InnoDB
attempts to limit the number of buffer pool load operations per second using theinnodb_io_capacity
setting. -
In MySQL 5.7.3, support is added to
InnoDB
for full-text parser plugins. For information about full-text parser plugins, see Full-Text Parser Plugins and Section 26.2.4.4, “Writing Full-Text Parser Plugins”. -
As of MySQL 5.7.4,
InnoDB
supports multiple page cleaner threads for flushing dirty pages from buffer pool instances. A new system variable,innodb_page_cleaners
, is used to specify the number of page cleaner threads. The default value of1
maintains the pre-MySQL 5.7.4 configuration in which there is a single page cleaner thread. This enhancement builds on work completed in MySQL 5.6, which introduced a single page cleaner thread to offload buffer pool flushing work from theInnoDB
master thread. -
As of MySQL 5.7.4, MySQL supports rebuilding regular and partitioned
InnoDB
tables using online DDL (ALGORITHM=INPLACE
) for the following operations:-
ALTER TABLE ... ENGINE=INNODB
(when run on anInnoDB
table)
Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduce user application downtime. For additional information, see Section 15.13.1, “Overview of Online DDL”.
-
The Fusion-io Non-Volatile Memory (NVM) file system on Linux provides atomic write capability, which makes the
InnoDB
doublewrite buffer redundant. In MySQL 5.7.4, theInnoDB
doublewrite buffer is automatically disabled for system tablespace files (ibdata files) located on Fusion-io devices that support atomic writes. -
As of MySQL 5.7.4,
InnoDB
supports the Transportable Tablespace feature for partitionedInnoDB
tables and individualInnoDB
table partitions. This enhancement eases backup procedures for partitioned tables and enables copying of partitioned tables and individual table partitions between MySQL instances. For additional information, see Section 15.7.6, “Copying File-Per-Table Tablespaces to Another Server”. -
As of MySQL 5.7.5, the
innodb_buffer_pool_size
parameter is dynamic, allowing you to resize the buffer pool without restarting the server. The resizing operation, which involves moving pages to a new location in memory, is performed in chunks. Chunk size is configurable using the newinnodb_buffer_pool_chunk_size
configuration option. You can monitor resizing progress using the newInnodb_buffer_pool_resize_status
status variable. For more information, see Configuring InnoDB Buffer Pool Size Online. -
Multi-threaded page cleaner support (
innodb_page_cleaners
) is extended to shutdown and recovery phases in MySQL 5.7.5. -
As of MySQL 5.7.5,
InnoDB
supports indexing of spatial data types usingSPATIAL
indexes, including use ofALTER TABLE ... ALGORITHM=INPLACE
for online operations (ADD SPATIAL INDEX
). -
As of MySQL 5.7.5,
InnoDB
performs a bulk load when creating or rebuilding indexes. This method of index creation is known as a “sorted index build”. This enhancement, which improves the efficiency of index creation, also applies to full-text indexes. A new global configuration option,innodb_fill_factor
, defines the percentage of space on each page that is filled with data during a sorted index build, with the remaining space reserved for future index growth. For more information, see Section 15.8.12, “Sorted Index Builds”. -
As of MySQL 5.7.5, A new log record type (
MLOG_FILE_NAME
) is used to identify tablespaces that have been modified since the last checkpoint. This enhancement simplifies tablespace discovery during crash recovery and eliminates scans on the file system prior to redo log application. For more information about the benefits of this enhancement, see Section 15.18.2, “Tablespace Discovery During Crash Recovery”.This enhancement changes the redo log format, requiring that MySQL be shut down cleanly before upgrading to or downgrading from MySQL 5.7.5.
-
As of MySQL 5.7.5, you can truncate undo logs that reside in undo tablespaces. This feature is enabled using the
innodb_undo_log_truncate
configuration option. For more information, see Section 15.7.8, “Truncating Undo Logs That Reside in Undo Tablespaces”. -
As of MySQL 5.7.6,
InnoDB
supports native partitioning. Previously,InnoDB
relied on theha_partition
handler, which creates a handler object for each partition. With native partitioning, a partitionedInnoDB
table uses a single partition-aware handler object. This enhancement reduces the amount of memory required for partitionedInnoDB
tables.As of MySQL 5.7.9, mysql_upgrade looks for and attempts to upgrade partitioned
InnoDB
tables that were created using theha_partition
handler. Also in MySQL 5.7.9 and later, you can upgrade such tables by name in the mysqlclient usingALTER TABLE ... UPGRADE PARTITIONING
. -
As of MySQL 5.7.6,
InnoDB
supports the creation of general tablespaces usingCREATE TABLESPACE
syntax.CREATE TABLESPACE `tablespace_name` ADD DATAFILE 'file_name.ibd' [FILE_BLOCK_SIZE = n]
General tablespaces can be created outside of the MySQL data directory, are capable of holding multiple tables, and support tables of all row formats.
Tables are added to a general tablespace using
CREATE TABLE
ortbl_name
... TABLESPACE [=]tablespace_name
ALTER TABLE
syntax.tbl_name
TABLESPACE [=]tablespace_name
For more information, see Section 15.7.9, “InnoDB General Tablespaces”.
-
In MySQL 5.7.9,
DYNAMIC
replacesCOMPACT
as the implicit default row format forInnoDB
tables. A new configuration option,innodb_default_row_format
, specifies the defaultInnoDB
row format. For more information, seeSection 15.11.2, “Specifying the Row Format for a Table”. -
As of MySQL 5.7.11,
InnoDB
supports data-at-rest encryption for file-per-table tablespaces. Encryption is enabled by specifying theENCRYPTION
option when creating or altering anInnoDB
table. This feature, referred to asInnoDB
tablespace encryption, relies on akeyring
plugin for encryption key management. For more information, see Section 7.5.3, “The MySQL Keyring”, and Section 15.7.10, “InnoDB Tablespace Encryption”.
-
-
JSON support. Beginning with MySQL 5.7.8, MySQL supports a native
JSON
type. JSON values are not stored as strings, instead using an internal binary format that permits quick read access to document elements. JSON documents stored inJSON
columns are automatically validated whenever they are inserted or updated, with an invalid document producing an error. JSON documents are normalized on creation, and can be compared using most comparison operators such as=
,<
,<=
,>
,>=
,<>
,!=
, and<=>
; for information about supported operators as well as precedence and other rules that MySQL follows when comparingJSON
values, see Comparison and Ordering of JSON Values.MySQL 5.7.8 also introduces a number of functions for working with
JSON
values. These functions include those listed here:-
Functions that create
JSON
values:JSON_ARRAY()
,JSON_MERGE()
, andJSON_OBJECT()
. See Section 13.16.2, “Functions That Create JSON Values”. -
Functions that search
JSON
values:JSON_CONTAINS()
,JSON_CONTAINS_PATH()
,JSON_EXTRACT()
,JSON_KEYS()
, andJSON_SEARCH()
. See Section 13.16.3, “Functions That Search JSON Values”. -
Functions that modify
JSON
values:JSON_APPEND()
,JSON_ARRAY_APPEND()
,JSON_ARRAY_INSERT()
,JSON_INSERT()
,JSON_QUOTE()
,JSON_REMOVE()
,JSON_REPLACE()
,JSON_SET()
, andJSON_UNQUOTE()
. See Section 13.16.4, “Functions That Modify JSON Values”. -
Functions that provide information about
JSON
values:JSON_DEPTH()
,JSON_LENGTH()
,JSON_TYPE()
, andJSON_VALID()
. See Section 13.16.5, “Functions That Return JSON Value Attributes”.
In MySQL 5.7.9 and later, you can use
as shorthand forcolumn
->path
JSON_EXTRACT(
. This works as an alias for a column wherever a column identifier can occur in an SQL statement, includingcolumn
,path
)WHERE
,ORDER BY
, andGROUP BY
clauses. This includesSELECT
,UPDATE
,DELETE
,CREATE TABLE
, and other SQL statements. The left hand side must be aJSON
column identifier (and not an alias). The right hand side is a quoted JSON path expression which is evaluated against the JSON document returned as the column value.See Section 13.16.3, “Functions That Search JSON Values”, for more information about
->
andJSON_EXTRACT()
. For information about JSON path support in MySQL 5.7, see Searching and Modifying JSON Values. See also Section 14.1.18.6, “Secondary Indexes and Generated Virtual Columns”. -
-
System and status variables. System and status variable information is now available in Performance Schema tables, in preference to use of
INFORMATION_SCHEMA
tables to obtain these variable. This also affects the operation of theSHOW VARIABLES
andSHOW STATUS
statements. The value of theshow_compatibility_56
system variable affects the output produced from and privileges required for system and status variable statements and tables. For details, see the description of that variable in Section 6.1.5, “Server System Variables”.NoteThe default for
show_compatibility_56
isOFF
. Applications that require 5.6 behavior should set this variable toON
until such time as they have been migrated to the new behavior for system variables and status variables. See Section 23.17, “Migrating to Performance Schema System and Status Variable Tables” -
sys schema. MySQL distributions now include the
sys
schema, which is a set of objects that help DBAs and developers interpret data collected by the Performance Schema.sys
schema objects can be used for typical tuning and diagnosis use cases. For more information, see Chapter 24, MySQL sys Schema. -
Condition handling. MySQL now supports stacked diagnostics areas. When the diagnostics area stack is pushed, the first (current) diagnostics area becomes the second (stacked) diagnostics area and a new current diagnostics area is created as a copy of it. Within a condition handler, executed statements modify the new current diagnostics area, but
GET STACKED DIAGNOSTICS
can be used to inspect the stacked diagnostics area to obtain information about the condition that caused the handler to activate, independent of current conditions within the handler itself. (Previously, there was a single diagnostics area. To inspect handler-activating conditions within a handler, it was necessary to check this diagnostics area before executing any statements that could change it.) See Section 14.6.7.3, “GET DIAGNOSTICS Syntax”, and Section 14.6.7.7, “The MySQL Diagnostics Area”. -
Optimizer. These optimizer enhancements were added:
-
EXPLAIN
can be used to obtain the execution plan for an explainable statement executing in a named connection:EXPLAIN [
options
] FOR CONNECTIONconnection_id
;For more information, see Section 9.8.4, “Obtaining Execution Plan Information for a Named Connection”.
-
It is possible to provide hints to the optimizer within individual SQL statements, which enables finer control over statement execution plans than can be achieved using the
optimizer_switch
system variable. Hints are also permitted in statements used withEXPLAIN
, enabling you to see how hints affect execution plans. For more information, see Section 9.9.3, “Optimizer Hints”.
-
-
Triggers. Previously, a table could have at most one trigger for each combination of trigger event (
INSERT
,UPDATE
,DELETE
) and action time (BEFORE
,AFTER
). This limitation has been lifted and multiple triggers are permitted. For more information, see Section 21.3, “Using Triggers”. -
Logging. These logging enhancements were added:
-
Previously, on Unix and Unix-like systems, MySQL support for sending the server error log to
syslog
was implemented by having mysqld_safe capture server error output and pass it tosyslog
. The server now includes nativesyslog
support, which has been extended to include Windows. For more information about sending server error output tosyslog
, see Section 6.4.2, “The Error Log”. -
The mysql client now has a
--syslog
option that causes interactive statements to be sent to the systemsyslog
facility. Logging is suppressed for statements that match the default “ignore” pattern list ("*IDENTIFIED*:*PASSWORD*"
), as well as statements that match any patterns specified using the--histignore
option. See Section 5.5.1.3, “mysql Logging”.
-
-
Generated Columns. MySQL now supports the specification of generated columns in
CREATE TABLE
andALTER TABLE
statements. Values of a generated column are computed from an expression specified at column creation time. Generated columns can be virtual (computed “on the fly” when rows are read) or stored (computed when rows are inserted or updated). For more information, see Section 14.1.18.5, “CREATE TABLE and Generated Columns”. -
mysql client. Previously, Control+C in mysql interrupted the current statement if there was one, or exited mysql if not. Now Control+C interrupts the current statement if there was one, or cancels any partial input line otherwise, but does not exit.
-
Database name rewriting with mysqlbinlog. Renaming of databases by mysqlbinlog when reading from binary logs written using the row-based format is now supported using the
--rewrite-db
option added in MySQL 5.7.1.This option uses the format
--rewrite-db='
. You can implement multiple rewrite rules, by specifying the option multiple times.dboldname
->dbnewname
' -
HANDLER with partitioned tables. The
HANDLER
statement may now be used with user-partitioned tables. Such tables may use any of the available partitioning types (see Section 20.2, “Partitioning Types”). -
Index condition pushdown support for partitioned tables. In MySQL 5.7.3 and later, queries on partitioned tables using the
InnoDB
orMyISAM
storage engine may employ the index condition pushdown optimization that was introduced in MySQL 5.6. See Section 9.2.1.6, “Index Condition Pushdown Optimization”, for more information. -
WITHOUT VALIDATION support for ALTER TABLE ... EXCHANGE PARTITION. As of MySQL 5.7.5,
ALTER TABLE ... EXCHANGE PARTITION
syntax includes an optional{WITH|WITHOUT} VALIDATION
clause. WhenWITHOUT VALIDATION
is specified,ALTER TABLE ... EXCHANGE PARTITION
does not perform row-by-row validation when exchanging a populated table with the partition, permitting database administrators to assume responsibility for ensuring that rows are within the boundaries of the partition definition.WITH VALIDATION
is the default behavior and need not be specified explicitly. For more information, see Section 20.3.3, “Exchanging Partitions and Subpartitions with Tables”. -
Master dump thread improvements. The master dump thread was refactored to reduce lock contention and improve master throughput. Previous to MySQL 5.7.2, the dump thread took a lock on the binary log whenever reading an event; in MySQL 5.7.2 and later, this lock is held only while reading the position at the end of the last successfully written event. This means both that multiple dump threads are now able to read concurrently from the binary log file, and that dump threads are now able to read while clients are writing to the binary log.
-
Globalization improvements. MySQL 5.7.4 includes a
gb18030
character set that supports the China National Standard GB18030 character set. For more information about MySQL character set support, see Section 11.1, “Character Set Support”. -
Changing the replication master without STOP SLAVE. In MySQL 5.7.4 and later, the strict requirement to execute
STOP SLAVE
prior to issuing anyCHANGE MASTER TO
statement is removed. Instead of depending on whether the slave is stopped, the behavior ofCHANGE MASTER TO
now depends on the states of the slave SQL thread and slave I/O threads; which of these threads is stopped or running now determines the options that can or cannot be used with aCHANGE MASTER TO
statement at a given point in time. The rules for making this determination are listed here:-
If the SQL thread is stopped, you can execute
CHANGE MASTER TO
using any combination ofRELAY_LOG_FILE
,RELAY_LOG_POS
, andMASTER_DELAY
options, even if the slave I/O thread is running. No other options may be used with this statement when the I/O thread is running. -
If the I/O thread is stopped, you can execute
CHANGE MASTER TO
using any of the options for this statement (in any allowed combination) exceptRELAY_LOG_FILE
,RELAY_LOG_POS
, orMASTER_DELAY
, even when the SQL thread is running. These three options may not be used when the I/O thread is running. -
Both the SQL thread and the I/O thread must be stopped before issuing
CHANGE MASTER TO ... MASTER_AUTO_POSITION = 1
.
You can check the current state of the slave SQL and I/O threads using
SHOW SLAVE STATUS
.If you are using statement-based replication and temporary tables, it is possible for a
CHANGE MASTER TO
statement following aSTOP SLAVE
statement to leave behind temporary tables on the slave. As part of this set of improvements, a warning is now issued wheneverCHANGE MASTER TO
is issued followingSTOP SLAVE
when statement-based replication is in use andSlave_open_temp_tables
remains greater than 0.For more information, see Section 14.4.2.1, “CHANGE MASTER TO Syntax”, and Section 18.3.8, “Switching Masters During Failover”.
-
-
Test suite. The MySQL test suite now uses
InnoDB
as the default storage engine. -
Multi-source replication is now possible. MySQL Multi-Source Replication adds the ability to replicate from multiple masters to a slave. MySQL Multi-Source Replication topologies can be used to back up multiple servers to a single server, to merge table shards, and consolidate data from multiple servers to a single server. See Section 18.1.4, “MySQL Multi-Source Replication”.
As part of MySQL Multi-Source Replication, replication channels have been added. Replication channels enable a slave to open multiple connections to replicate from, with each channel being a connection to a master. See Section 18.2.3, “Replication Channels”.
-
Group Replication Performance Schema tables. MySQL 5.7 adds a number of new tables to the Performance Schema to provide information about replication groups and channels. These include the following tables:
All of these tables were added in MySQL 5.7.2, except for
replication_group_members
andreplication_group_member_stats
, which were added in MySQL 5.7.6. For more information, see Section 23.9.11, “Performance Schema Replication Tables”. -
Group Replication SQL. The following statements were added in MySQL 5.7.6 for controlling group replication:
For more information, see Section 14.4.3, “SQL Statements for Controlling Group Replication”.
The following features are deprecated in MySQL 5.7 and may be or will be removed in a future series. Where alternatives are shown, applications should be updated to use them.
-
The
ERROR_FOR_DIVISION_BY_ZERO
,NO_ZERO_DATE
, andNO_ZERO_IN_DATE
SQL modes are now deprecated but enabled by default. The long term plan is to have them included in strict SQL mode and to remove them as explicit modes in a future MySQL release.The deprecated
ERROR_FOR_DIVISION_BY_ZERO
,NO_ZERO_DATE
, andNO_ZERO_IN_DATE
SQL modes are still recognized so that statements that name them do not produce an error, but will be removed in a future version of MySQL. To make advance preparation for versions of MySQL in which these mode names do not exist, applications should be modified to not refer to them. See SQL Mode Changes in MySQL 5.7. -
Changes to account-management statements make the following features obsolete. They are now deprecated:
-
Using
GRANT
to create users. Instead, useCREATE USER
. Following this practice makes theNO_AUTO_CREATE_USER
SQL mode immaterial forGRANT
statements, so it too is deprecated. -
Using
GRANT
to modify account properties other than privilege assignments. This includes authentication, SSL, and resource-limit properties. Instead, establish such properties at account-creation time withCREATE USER
or modify them afterward withALTER USER
. -
IDENTIFIED BY PASSWORD '
syntax forhash_string
'CREATE USER
andGRANT
. Instead, useIDENTIFIED WITH
forauth_plugin
AS 'hash_string
'CREATE USER
andALTER USER
, where the'
value is in a format compatible with the named plugin.hash_string
' -
The
PASSWORD()
function is deprecated and should be avoided in any context. Thus,SET PASSWORD ... = PASSWORD('
syntax is also deprecated.auth_string
')SET PASSWORD ... = '
syntax is not deprecated; nevertheless,auth_string
'ALTER USER
is now the preferred statement for assigning passwords. -
The
old_passwords
system variable. Account authentication plugins can no longer be left unspecified in themysql.user
table, so any statement that assigns a password from a cleartext string can unambiguously determine the hashing method to use on the string before storing it in themysql.user
table. This rendersold_passwords
superflous.
-
-
Relying on implicit
GROUP BY
sorting in MySQL 5.7 is deprecated. To achieve a specific sort order of grouped results, it is preferable to use an explicitORDER BY
clause.GROUP BY
sorting is a MySQL extension that may change in a future release; for example, to make it possible for the optimizer to order groupings in whatever manner it deems most efficient and to avoid the sorting overhead. -
The
EXTENDED
andPARTITIONS
keywords for theEXPLAIN
statement are deprecated. These keywords are still recognized but are now unnecessary because their effect is always enabled. -
The
--skip-innodb
option and its synonyms (--innodb=OFF
,--disable-innodb
, and so forth) are deprecated. These options have no effect as of MySQL 5.7. becauseInnoDB
cannot be disabled. -
The client-side
--ssl
and--ssl-verify-server-cert
options are deprecated. Use--ssl-mode=REQUIRED
instead of--ssl=1
or--enable-ssl
. Use--ssl-mode=DISABLED
instead of--ssl=0
,--skip-ssl
, or--disable-ssl
. Use--ssl-mode=VERIFY_IDENTITY
instead of--ssl-verify-server-cert
options. (The server-side--ssl
option is not deprecated.)For the C API,
MYSQL_OPT_SSL_ENFORCE
andMYSQL_OPT_SSL_VERIFY_SERVER_CERT
options formysql_options()
correspond to the client-side--ssl
and--ssl-verify-server-cert
options and are deprecated. UseMYSQL_OPT_SSL_MODE
with an option value ofSSL_MODE_REQUIRED
orSSL_MODE_VERIFY_IDENTITY
instead. -
The
log_warnings
system variable and--log-warnings
server option are deprecated. Use thelog_error_verbosity
system variable instead. -
The
binlog_max_flush_queue_time
system variable does nothing in MySQL 5.7, and is deprecated as of MySQL 5.7.9. -
The
innodb_support_xa
system variable, which enablesInnoDB
support for two-phase commit in XA transactions, is deprecated as of MySQL 5.7.10.InnoDB
support for two-phase commit in XA transactions is always enabled as of MySQL 5.7.10. -
The
metadata_locks_cache_size
andmetadata_locks_hash_instances
system variables are deprecated. These do nothing as of MySQL 5.7.4. -
The
sync_frm
system variable is deprecated. -
The global
character_set_database
andcollation_database
system variables are deprecated and will be removed in a future version of MySQL.Assigning a value to the session
character_set_database
andcollation_database
system variables is deprecated and assignments produce a warning. The session variables will become read only in a future version of MySQL and assignments will produce an error. It will remain possible to access the session variables to determine the database character set and collation for the default database. -
The
ENCRYPT()
,ENCODE()
,DECODE()
,DES_ENCRYPT()
, andDES_DECRYPT()
encryption functions are deprecated. Consider usingAES_ENCRYPT()
andAES_DECRYPT()
instead. -
The
MBREqual()
spatial function is deprecated. UseMBREquals()
instead. -
The
INFORMATION_SCHEMA
PROFILING
table is deprecated. Use the Performance Schema instead; see Chapter 23, MySQL Performance Schema. -
The
INFORMATION_SCHEMA
INNODB_LOCKS
andINNODB_LOCK_WAITS
tables are deprecated, to be removed in MySQL 8.0, which provides replacement Performance Schema tables. -
mysqld_safe support for
syslog
output is deprecated. Use the native serversyslog
support used instead. See Section 6.4.2, “The Error Log”. -
Conversion of pre-MySQL 5.1 database names containing special characters to 5.1 format with the addition of a
#mysql50#
prefix is deprecated. Because of this, the--fix-db-names
and--fix-table-names
options for mysqlcheck and theUPGRADE DATA DIRECTORY NAME
clause for theALTER DATABASE
statement are also deprecated.Upgrades are supported only from one release series to another (for example, 5.0 to 5.1, or 5.1 to 5.5), so there should be little remaining need for conversion of older 5.0 database names to current versions of MySQL. As a workaround, upgrade a MySQL 5.0 installation to MySQL 5.1 before upgrading to a more recent release.
-
mysql_install_db functionality has been integrated into the MySQL server, mysqld. To use this capability to initialize a MySQL installation, if you previously invoked mysql_install_db manually, invoke mysqld with the
--initialize
or--initialize-insecure
option, depending on whether you want the server to generate a random password for the initial'root'@'localhost'
account.mysql_install_db is now deprecated, as is the special
--bootstrap
option that mysql_install_db passes to mysqld. -
The mysql_plugin utility is deprecated. Alternatives include loading plugins at server startup using the
--plugin-load
or--plugin-load-add
option, or at runtime using theINSTALL PLUGIN
statement. -
The
mysql_kill()
,mysql_list_fields()
,mysql_list_processes()
, andmysql_refresh()
C API functions are deprecated. The same is true of the correspondingCOM_PROCESS_KILL
,COM_FIELD_LIST
,COM_PROCESS_INFO
, andCOM_REFRESH
client/server protocol commands. Instead, usemysql_query()
to execute aKILL
,SHOW COLUMNS
,SHOW PROCESSLIST
, orFLUSH
statement, respectively.
The following items are obsolete and have been removed in MySQL 5.7. Where alternatives are shown, applications should be updated to use them.
-
Support for passwords that use the older pre-4.1 password hashing format is removed, which involves the following changes. Applications that use any feature no longer supported must be modified.
-
The
mysql_old_password
authentication plugin is removed. Accounts that use this plugin are disabled at startup and the server writes an “unknown plugin” message to the error log. For instructions on upgrading accounts that use this plugin, see Section 7.5.1.3, “Migrating Away from Pre-4.1 Password Hashing and the mysql_old_password Plugin”. -
The
--secure-auth
option to the server and client programs is the default, but is now a no-op. It is deprecated and will be removed in a future MySQL release. -
The
--skip-secure-auth
option to the server and client programs is no longer supported and using it produces an error. -
The
secure_auth
system variable permits only a value of 1; a value of 0 is no longer permitted. -
For the
old_passwords
system variable, a value of 1 (produce pre-4.1 hashes) is no longer permitted. -
The
OLD_PASSWORD()
function is removed.
-
-
In MySQL 5.6.6, the
YEAR(2)
data type was deprecated. Support forYEAR(2)
is now removed. Once you upgrade to MySQL 5.7.5 or higher, any remainingYEAR(2)
columns must be converted toYEAR(4)
to become usable again. For conversion strategies, see Section 12.3.4, “YEAR(2) Limitations and Migrating to YEAR(4)”. For example, run mysql_upgrade after upgrading. -
The
innodb_mirrored_log_groups
system variable. The only supported value was 1, so it had no purpose. -
The
storage_engine
system variable. Usedefault_storage_engine
instead. -
The
thread_concurrency
system variable. -
The
timed_mutexes
system variable. It does nothing and has no effect. -
The
IGNORE
clause forALTER TABLE
. -
INSERT DELAYED
is no longer supported. The server recognizes but ignores theDELAYED
keyword, handles the insert as a nondelayed insert, and generates anER_WARN_LEGACY_SYNTAX_CONVERTED
warning. (“INSERT DELAYED is no longer supported. The statement was converted to INSERT.”) Similarly,REPLACE DELAYED
is handled as a nondelayed replace. TheDELAYED
keyword will be removed in a future release.In addition, several
DELAYED
-related options or features were removed:-
The
--delayed-insert
option for mysqldump. -
The
COUNT_WRITE_DELAYED
,SUM_TIMER_WRITE_DELAYED
,MIN_TIMER_WRITE_DELAYED
,AVG_TIMER_WRITE_DELAYED
, andMAX_TIMER_WRITE_DELAYED
columns of the Performance Schematable_lock_waits_summary_by_table
table. -
mysqlbinlog no longer writes comments mentioning
INSERT DELAYED
.
-
-
Database symlinking on Windows using for
.sym
files has been removed because it is redundant with native symlink support available using mklink. Any.sym
file symbolic links will be ignored and should be replaced with symlinks created using mklink. See Section 9.12.3.3, “Using Symbolic Links for Databases on Windows”. -
The unused
--basedir
,--datadir
, and--tmpdir
options for mysql_upgrade were removed. -
Previously, program options could be specified in full or as any unambiguous prefix. For example, the
--compress
option could be given to mysqldump as--compr
, but not as--comp
because the latter is ambiguous. Option prefixes are no longer supported; only full options are accepted. This is because prefixes can cause problems when new options are implemented for programs and a prefix that is currently unambiguous might become ambiguous in the future. Some implications of this change:-
The
--key-buffer
option must now be specified as--key-buffer-size
. -
The
--skip-grant
option must now be specified as--skip-grant-tables
.
-
-
SHOW ENGINE INNODB MUTEX
output is removed in MySQL 5.7.2. Comparable information can be generated by creating views on Performance Schema tables. -
The
InnoDB
Tablespace Monitor andInnoDB
Table Monitor are removed in MySQL 5.7.4. For the Tablespace Monitor, equivalent functionality will be introduced before the GA release of MySQL 5.7. For the Table Monitor, equivalent information can be obtained fromInnoDB
INFORMATION_SCHEMA
tables. -
The specially named tables used to enable and disable the standard
InnoDB
Monitor andInnoDB
Lock Monitor (innodb_monitor
andinnodb_lock_monitor
) are removed in MySQL 5.7.4 and replaced by two dynamic system variables:innodb_status_output
andinnodb_status_output_locks
. For additional information, see Section 15.17, “InnoDB Monitors”. -
The
innodb_use_sys_malloc
andinnodb_additional_mem_pool_size
system variables, which were deprecated in MySQL 5.6.3, are removed in MySQL 5.7.4. -
The msql2mysql, mysql_convert_table_format, mysql_find_rows, mysql_fix_extensions, mysql_setpermission, mysql_waitpid, mysql_zap, mysqlaccess, and mysqlbug utilities.
-
The mysqlhotcopy utility. Alternatives include mysqldump and MySQL Enterprise Backup.
-
The binary-configure.sh script.
-
The
INNODB_PAGE_ATOMIC_REF_COUNT
CMake option is removed in MySQL 5.7.5. -
The
innodb_create_intrinsic
option is removed in MySQL 5.7.6. -
The
innodb_optimize_point_storage
option and related internal data types (DATA_POINT
andDATA_VAR_POINT
) were removed. -
The
innodb_log_checksum_algorithm
option is removed in MySQL 5.7.9.
-
-
Apache HTTP Server 2.4.23
Changes with Apache 2.4.23 *) mod_ssl: reset client-verify state of ssl when aborting renegotiations. [Erki Aring <erki@example.ee>, Stefan Eissing] *) mod_sed: Fix 'x' command processing. [Christophe Jaillet] *) configure: Fix ./configure edge-case failures around dependencies of mod_proxy_hcheck. [William Rowe, Ruediger Pluem, Jeff Trawick]
-
-
-
-
-
-
-
-
-
Vultr 50$
in Προσφορές και εκπτώσεις
Posted · Report reply
$50 Free On Us!
Receive $50 in Vultr credit and test drive our high performance cloud
What's included?
$50 in credit to launch instances and one click applications on the Vultr Cloud. Our free trial gives you full access to Vultr to launch instances around the globe and test drive our platform.
https://www.vultr.com/freetrial/