https://stackoverflow.com/questions/63179173/gatsby-source-graphql-only-shows-10-results
I was experiencing the same issue with Graphql only returning the first 10 comments. I was able to get around this issue by specifying a first value in my query.
query {
comments (first: 500) {
...
}
}
The current GraphQL Edge schema likely has 10 as a default value for first.
https://stackoverflow.com/questions/31163693/how-do-i-conditionally-add-attributes-to-react-components
Apparently, for certain attributes, React is intelligent enough to omit the attribute if the value you pass to it is not truthy. For example:
const InputComponent = function() {
const required = true;
const disabled = false;
return (
<input type="text" disabled={disabled} required={required} />
);
}
will result in:
<input type="text" required>
Update: if anyone is curious as to how/why this happens, you can find details in ReactDOM's source code, specifically at lines 30 and 167 of the DOMProperty.js file.
https://stackoverflow.com/questions/5135019/css-opacity-only-to-background-color-not-the-text-on-it
It sounds like you want to use a transparent background, in which case you could try using the rgba() function:
rgba(R, G, B, A)R (red), G (green), and B (blue) can be either
<integer>s or<percentage>s, where the number 255 corresponds to 100%. A (alpha) can be a<number>between 0 and 1, or a<percentage>, where the number 1 corresponds to 100% (full opacity).RGBa example
background: rgba(51, 170, 51, .1) /* 10% opaque green */ background: rgba(51, 170, 51, .4) /* 40% opaque green */ background: rgba(51, 170, 51, .7) /* 70% opaque green */ background: rgba(51, 170, 51, 1) /* full opaque green */
A small example showing how rgba can be used.
https://www.ryadel.com/en/mariadb-10-upgrade-10-3-without-losing-data-how-to/
The first thing to do is to perform a full backup of the whole MariaDB server instance. To do so, I strongly suggest you to read this MySQL/MariaDB backup tutorial using the free mysqldump command-line tool. In very short words, here’s the one-liner:
1 | # mysqldump -u db_root_user -p -x -A > /bak/db_backup.sql |
Table of Contents [hide]
It has been a while since MariaDB 10.3 has been out, bringing its stunning pack of changes, improvements and new features – most notably, System-versioned tables and Sequences. If you found this post on Google, there’s a high chance you want to upgrade your previous version of MariaDB and take advantage of these awesome new feats.
In this article, we’ll see how we can safely update any existing 10.0, 10.1 or 10.2 MariaDB instance with the new MariaDB 10.3 – more specifically, MariaDB 10.3.13-GA, which has been released on 2018-07-03 and is the latest stable version as of today. The steps below have been tested on a Linux CentOS 7 machine, but can be used – or slightly adapted by replacing yum with apt-get – with most Linux distributions.
The first thing to do is to perform a full backup of the whole MariaDB server instance. To do so, I strongly suggest you to read this MySQL/MariaDB backup tutorial using the free mysqldump command-line tool. In very short words, here’s the one-liner:
If everything goes well, you won’t need this backup: however, since we’re performing a DB upgrade here, it’s better to be safe than sorry.
The next thing to do is to shutdown the existing MariaDB server. This can be done with the following command:
This step might sound scary, but don’t worry: your existing databases and your current my.cnf file won’t be deleted, only the binaries will.
# sudo yum remove mariadb mariadb-server
As soon as the previous MariaDB instance is gone, we need to install the new version: in order to do that, we need to tell our Linux machine where to find the updated binaries. If you’re using CentOS, RHEL or another yum-based distribution, you can easily do that by creating a new MariaDB10.repo file to the /etc/yum.repos.d/ folder and filling it with the following content:
In case you already have a MariaDB.repo, MariaDB10.repo or some other .repo file pointing to the old binaries, you might as well update it with the new 10.3 URIs.
Now that yum will find the new binaries, we can proceed installing the new MariaDB server with the following command:
This will install both the client and the server.
Once the installation job is complete, you can restart and enable the new MariaDB server with the following commands:
Last but not least, you need to run the mysql_upgrade command to upgrade the permission tables in the mysql database with some new fields:
This command will also perform a very quick check of all tables and marks them as compatible with MariaDB 10.3.
That’s about it: I sincerely hope that this small tutorial will help you upgrading to MariaDB 10.3 and enjoy its new exciting features!