doc.php | php filebrowser with markdown parser

1. Dump the schema only via mysqldump --no-data
2. Load that schema in another database or server.
3. Write all the ALTERs that you will ultimately need.
4. Performs the ALTERs. This will show you what problems you will have.

Other tips:

• Don't use TINYTEXT for anything. Either use a VARCHAR or a bigger TEXT.
• See this for 5 workarounds for the 767 problem you described: http://mysql.rjweb.org/doc.php/limits#767_limit_in_innodb_indexes
• That link also provides a tip on creating the set of ALTER...CONVERT TO that you need.
• When using CONVERT TO, keep in mind that it changes all the text columns; this may not be desired if you have some columns that are deliberately ascii such as postal_code, md5, uuid, etc.

The biggest difference, is of course that phpmyadmin adds a LIMIT to the query. That gives the main explanation. I can't believe that that wasn't the first thing we tried, I am very embarrassed.

However, the speed difference between phpMyAdmin and mysqli is still big, and the results are still different (2020-05-01 on server or mysqli):

That is a warning, designed to protect people from unknowingly allowing private responses to be cached. Those descriptions all say some variation of "If sensitive information is stored in the cache...". Note the "If".

If you are knowingly allowing the content to be cached, then there's no problem. I assume the tool is showing this only on secure requests because of a presumption that such information might be sensitive.

The problem with your first code snippet is that the text you're passing as a parameter to the HTTP call is too long, if you print the response object you'll see:

that corresponds to 414 URI Too Long Reference

If you pass a smaller text, dbpedia-spotlight will be able to annotate the entities for you.

For the second code that you put, you have two problems, the first one is that dbpedia-spotlight may respond with 403 status after consecutive calls to the annotate service, to check that I suggest you to do:

Using GNU awk:

Update:

The problem as mentioned in Xmlhttp request is raising an Access Denied error is you need to use the Server version of XMLHTTP that isn't restricted to accessing sites trusted by IE and restricted by the IE security policies. This is because XMLHTTP is designed for client-side whereas ServerXMLHTTP is specifically designed for server-side usage.

Textual info is located in [text] properties, which in their turn are nested in [elements] properties. Just search for them in the object you get in your browser using the "find something in text" function of your browser, to see the text you are searching for.

These two properties are protected, so you will have to make them public, in order to access/extract them.

Where these properties are defined within the PHPWord library: https://stackoverflow.com/a/50989007/8510094

Once you have made them public, you can start cutting off every layer of the object you have received and thus access the object where [elements]->[text] properties are just one layer down the 'tree'.

So, the algorithm is to 1) find these [text] properties, 2) see the path to the object holding these properties, 3) cut off higher-level objects and arrays level by level, 4) get an object where [elements]->[text] properties are just the 2nd level, 5) gather all the values of [text] properties in, say, an array.

Don't try to use foreach loops, recursive functions, etc. trying to access the text. The resulting object is enormous. You won't be given memory or time this big to be able to iterate over, flatten, reduce, etc. such big multidimensional associative arrays of data.

Alternatively, you can make certain changes to the PHPWord library files and don't get unnecessary properties and values in the resulting object you get when you load your Word file into PHPWord (styles, paragraph info, etc.).

In PHPSpreadsheet, they implemented a method to get only actual data from Excel files (stripped of formatting, styles info, etc). On the other hand, PHPWord also declared $readDataOnly property, but they stopped just there, and for some reason didn't implement the mechanism to read actual, textual data only.

That is actually an issue with bad documentation for the SVG.js library. If you define a transformation as