summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRoeland Jago Douma <rullzer@users.noreply.github.com>2019-11-20 21:51:16 +0100
committerGitHub <noreply@github.com>2019-11-20 21:51:16 +0100
commit2eb24fcf420acae5f62e7a4d8190b74d9c701d0f (patch)
tree438a1312d3f3134dc0eb68090e87cf72eef82cd5
parente358d79114ae7a17e418385e75130d56e5dc7fb5 (diff)
parent77d814d35f4db0cdff8b88542c31f268a76fec71 (diff)
downloadnextcloud-server-2eb24fcf420acae5f62e7a4d8190b74d9c701d0f.tar.gz
nextcloud-server-2eb24fcf420acae5f62e7a4d8190b74d9c701d0f.zip
Merge pull request #18009 from nextcloud/bugfix/noid/install-with-mysql-8.0.4+
Fix installing with MySQL 8.0.4+
-rw-r--r--lib/private/Setup/MySQL.php4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/private/Setup/MySQL.php b/lib/private/Setup/MySQL.php
index eb4fedefd4b..3bb940186f8 100644
--- a/lib/private/Setup/MySQL.php
+++ b/lib/private/Setup/MySQL.php
@@ -100,9 +100,9 @@ class MySQL extends AbstractDatabase {
$password = $this->dbPassword;
// we need to create 2 accounts, one for global use and one for local user. if we don't specify the local one,
// the anonymous user would take precedence when there is one.
- $query = "CREATE USER '$name'@'localhost' IDENTIFIED BY '$password'";
+ $query = "CREATE USER '$name'@'localhost' IDENTIFIED WITH mysql_native_password BY '$password'";
$connection->executeUpdate($query);
- $query = "CREATE USER '$name'@'%' IDENTIFIED BY '$password'";
+ $query = "CREATE USER '$name'@'%' IDENTIFIED WITH mysql_native_password BY '$password'";
$connection->executeUpdate($query);
}
catch (\Exception $ex){
an>FOP's "intermediate format". More information on that can be found on the page dedicated to the <a href="intermediate.html">Intermediate Format</a>. </p> </section> <section id="awt"> <title>Java2D/AWT</title> <p> The Java2DRenderer provides the basic functionality for all Java2D-based output formats (AWT viewer, direct print, PNG, TIFF). </p> <p> The AWT viewer shows a window with the pages displayed inside a Java graphic. It displays one page at a time. The fonts used for the formatting and viewing depend on the fonts available to your JRE. </p> </section> <section id="print"> <title>Print</title> <p> It is possible to directly print the document from the command line. This is done with the same code that renders to the Java2D/AWT renderer. </p> </section> <section id="bitmap"> <title>Bitmap (TIFF/PNG)</title> <p> It is possible to directly create bitmap images from the individual pages generated by the layout engine. This is done with the same code that renders to the Java2D/AWT renderer. </p> <p> Currently, two output formats are supported: PNG and TIFF. TIFF produces one file with multiple pages, while PNG output produces one file per page. The quality of the bitmap depends on the target resolution setting on the FOUserAgent. </p> <section id="bitmap-configuration"> <title>Configuration</title> <p> The TIFF and PNG renderer configuration currently allows the following settings: </p> <source><![CDATA[<renderer mime="image/png"> <transparent-page-background>true</transparent-page-background> <fonts><!-- described elsewhere --></fonts> </renderer>]]></source> <p> The default value for the "transparent-page-background" setting is "false" which paints an opaque, white background for the whole image. If you set this to true, no such background will be painted and you will get a transparent image if an alpha channel is available in the output format. </p> </section> <section id="tiff-configuration"> <title>TIFF-specific Configuration</title> <p> In addition to the above values the TIFF renderer configuration allows some additional settings: </p> <source><![CDATA[<renderer mime="image/tiff"> <transparent-page-background>true</transparent-page-background> <compression>CCITT T.6</compression> <fonts><!-- described elsewhere --></fonts> </renderer>]]></source> <p> The default value for the "compression" setting is "PackBits" which which is a widely supported RLE compression scheme for TIFF. The set of compression names to be used here matches the set that the Image I/O API uses. Note that not all compression schemes may be available during runtime. This depends on the actual codecs being available. Here is a list of possible values: </p> <ul> <li>NONE (no compression)</li> <li>PackBits (RLE, run-length encoding)</li> <li>JPEG</li> <li>Deflate</li> <li>LZW</li> <li>ZLib</li> <li>CCITT T.4 (Fax Group 3)</li> <li>CCITT T.6 (Fax Group 4)</li> </ul> <note> If you want to use CCITT compression, please make sure you've got a J2SE 1.4 or later and <a href="http://java.sun.com/products/java-media/jai/current.html"> Java Advanced Imaging Image I/O Tools </a> in your classpath. The Sun JRE doesn't come with a TIFF codec built in, so it has to be added separately. The internal TIFF codec from XML Graphics Commons only supports PackBits, Deflate and JPEG compression for writing. </note> </section> </section> <section id="txt"> <title>TXT</title> <p> The text renderer produces plain ASCII text output that attempts to match the output of the PDFRenderer as closely as possible. This was originally developed to accommodate an archive system that could only accept plain text files, and is primarily useful for getting a quick-and-dirty view of the document text. The renderer is very limited, so do not be surprised if it gives unsatisfactory results. </p> <p> The Text renderer works with a fixed size page buffer. The size of this buffer is controlled with the textCPI and textLPI public variables. The textCPI is the effective horizontal characters per inch to use. The textLPI is the vertical lines per inch to use. From these values and the page width and height the size of the buffer is calculated. The formatting objects to be rendered are then mapped to this grid. Graphic elements (lines, borders, etc) are assigned a lower priority than text, so text will overwrite any graphic element representations. </p> <p> Because FOP lays the text onto a grid during layout, there are frequently extra or missing spaces between characters and lines, which is generally unsatisfactory. Users have reported that the optimal settings to avoid such spacing problems are: </p> <ul> <li>font-family="Courier"</li> <li>font-size="7.3pt"</li> <li>line-height="10.5pt"</li> </ul> </section> <section id="sandbox"> <title>Output Formats in the Sandbox</title> <p> Due to the state of certain renderers we moved some of them to a "sandbox" area until they are ready for more serious use. The renderers and FOEventHandlers in the sandbox can be found under src/sandbox and are compiled into build/fop-sandbox.jar during the main build. The output formats in the sandbox are marked as such below. </p> <section id="mif"> <title>MIF</title> <warning>The MIF handler is in the sandbox and not yet functional in FOP Trunk!!! Please help us ressurrect this feature.</warning> <p> This format is the Maker Interchange Format which is used by Adobe Framemaker. </p> </section> <section id="svg"> <title>SVG</title> <warning>The SVG renderer is in the sandbox and may not work as expected in FOP Trunk!!! Please help us improve this feature.</warning> <p> This format creates an SVG document that has links between the pages. This is primarily for slides and creating svg images of pages. Large documents will create SVG files that are far too large for an SVG viewer to handle. Since FO documents usually have text the SVG document will have a large number of text elements. The font information for the text is obtained from the JVM in the same way as for the AWT viewer. If the SVG is viewed on a system where the fonts are different, such as another platform, then the page may look wrong. </p> </section> </section> <section id="wishlist"> <title>Wish list</title> <p> Apache FOP is easily extensible and allows you to add new output formats to enhance FOP's functionality. There's a number of output formats which are on our wish list. We're looking for volunteers to help us implement them. </p> <ul> <li> <a href="http://en.wikipedia.org/wiki/OpenDocument">ODF (Open Document Format)</a>: The standardized successor to OpenOffice's file format. </li> </ul> </section> </body> </document>